> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/integrations-and-automation-templates/n8n/n8n-basics.md).

# 1 Post Everywhere

Publish a first authorized post from n8n, retain its submission ID, and verify completion before expanding to more destinations.

### How It Works

Start with the user's requested destination and content. A publish response accepts work into the queue. Marking a Google Sheet row as "Posted" requires a verified publication, not only a successful Publish node execution.

## First verified publication

1. [Install the Blotato node](/integrations-and-automation-templates/n8n/n8n-blotato-node.md#install-the-blotato-node).
2. [Configure and verify its credential](/integrations-and-automation-templates/n8n/n8n-blotato-node.md#configure-and-verify-the-credential).
3. Add the Blotato Post > Publish operation.
4. Select the requested platform and current account.
5. Select the destination Page or board when required. Follow [Account IDs](/api-and-mcp-concepts/accounts-and-identifiers.md).
6. Map the authorized text and media URLs. Follow the destination's [publishing requirements](/platform-publishing/platforms.md).
7. Execute the Publish node only after the user authorizes this publication.
8. Save the returned `postSubmissionId` for that destination.
9. Use Post > Get with that ID.
10. Route the returned state using the [publication checks](/integrations-and-automation-templates/n8n/n8n-blotato-node.md#verify-a-publication).

For a public image or video URL, pass it directly in `mediaUrls`. No upload step required. For local file bytes or a private Google Drive share link, follow [Media uploads](/api-and-mcp-concepts/media-uploads-and-conversion.md) first.

## Expand to more destinations

1. Add only the destinations requested by the user.
2. Map each destination's current account and required fields separately.
3. Keep a separate submission ID and outcome for every destination.
4. Report partial success if some destinations publish while others fail or remain pending.

Do not rerun the entire fan-out to recover one destination. Do not automatically activate a daily schedule when the user requested a single post. Follow [Publishing status](/start-with-an-ai-agent/publishing-status.md) for recovery.

### Tutorials

These tutorials show a Google Sheets and Google Drive automation. Use the current steps and completion checks above when adapting an older workflow. Watching the videos is not required for an AI agent to perform the task.

* Youtube tutorial: <https://youtu.be/AB_5ifmBqec?si=2f5jQeEhoz5Y8YWM>
* Newsletter tutorial: <https://www.sabrina.dev/p/easy-social-media-posting-n8n-make>
* Template: <https://drive.google.com/drive/folders/1YphrE-bclOAxsq33cVQ1Ku-NmhQ0dJxv?usp=drive_link>

{% embed url="<https://youtu.be/AB_5ifmBqec>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/integrations-and-automation-templates/n8n/n8n-basics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.