> 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-blotato-node.md).

# n8n Blotato Node

Install the Blotato n8n node, configure its API credential, verify access, and check asynchronous results.

The official Blotato community node for n8n: <https://github.com/Blotato-Inc/n8n-nodes-blotato>

***

## Available Operations

The Blotato node supports the following operations:

| Resource | Operation | Description                                           |
| -------- | --------- | ----------------------------------------------------- |
| Post     | Publish   | Publish a post to social platforms                    |
| Post     | Get       | Check a post submission's status                      |
| Media    | Upload    | Upload media files                                    |
| Visual   | Create    | Create visuals from templates (carousels, slideshows) |
| Visual   | Get       | Get visual creation status                            |
| Visual   | Delete    | Delete a visual after the user's authorization        |
| Source   | Create    | Resolve content from URLs, text, PDFs, etc.           |
| Source   | Get       | Get source resolution status and content              |

***

## Install the Blotato Node

### n8n Cloud Users

1. Use an n8n instance owner or admin account for installation.
2. Open a workflow's node panel.
3. Search for "Blotato".
4. Select the node under "More from the community".
5. Click Install.

If community results are hidden, ask the instance owner to check the verified-community-node setting in the Cloud Admin Panel. Members use nodes after an owner or admin installs them. See [n8n's installation instructions](https://docs.n8n.io/integrations/community-nodes/installation-and-management/install-verified-community-nodes).

### Self-Hosted n8n Users

1. Use an n8n instance owner or admin account.
2. Open Settings > Community Nodes.
3. Click Install.
4. Enter the package name `n8n-nodes-blotato`.
5. Review the package and confirm installation.

If community packages are disabled, ask the instance administrator to review `N8N_COMMUNITY_PACKAGES_ENABLED`. Its default is `true`. Change deployment settings or restart n8n only with the administrator's approval. See [n8n's community-node settings](https://docs.n8n.io/hosting/configuration/environment-variables/nodes/) and [installation guide](https://docs.n8n.io/integrations/community-nodes/installation-and-management/gui-installation).

***

## Update the Blotato Node

1. Go to n8n Settings > Community Nodes
2. Find the Blotato node and click Options
3. Click Update

***

## Configure and verify the credential

1. Connect the intended social accounts in [Accounts](https://my.blotato.com/accounts).
2. Read [API access and authentication](/api-and-mcp-concepts/authentication.md) before generating a key. Generating a key during a free trial starts paid access.
3. Create or select the node's "Blotato API" credential.
4. Enter the key in its "API Key" field. Do not paste it into workflow text, documentation, or chat.
5. Keep "Blotato Server" set to `https://backend.blotato.com`. Do not append `/v2`; the node adds the endpoint path.
6. Save and test the credential.
7. Refresh the account selection in a Publish node and select the intended platform and account.

The credential test calls `GET /v2/users/me`. Passing it proves authentication, not a completed publication. Verify the account selection separately. If no accounts appear, inspect [account lookup](/api-and-mcp-concepts/accounts-and-identifiers.md) rather than creating a test post.

## Verify a publication

1. After an authorized Post > Publish call, retain `postSubmissionId`.
2. Use Post > Get with that ID.
3. For `in-progress`, wait at least 10 seconds before another check within a bounded wait.
4. For `scheduled`, report the scheduled time rather than publication.
5. For `published`, return `publicUrl` if provided.
6. For `failed`, report `errorMessage` and follow [publishing diagnosis](/start-with-an-ai-agent/publishing-status.md).

If the installed node lacks Get, use an authenticated HTTP request to `GET /v2/posts/{postSubmissionId}`. An `in-progress` response is not a queue-health check. Do not repeat Publish because a status check failed.

## Using Source Operations

Source creation and extraction are separate operations. Retain the returned ID and check the result before using its content.

### Supported Source Types

| Node choice | Input          | Behavior                                                                                  |
| ----------- | -------------- | ----------------------------------------------------------------------------------------- |
| URL         | A source URL   | The node infers YouTube, TikTok, PDF, or audio from the URL and otherwise uses `article`. |
| Text        | Text           | Sends the text source type.                                                               |
| AI Research | Research query | Sends the `perplexity-query` source type.                                                 |

These are the n8n node's choices, not the REST `sourceType` enum. For explicit type selection, including `twitter`, use the [Create Source REST contract](/rest-api-reference/create-source.md) in an HTTP Request node. Inspect the request if URL inference chooses the wrong type.

### Create Source

1. Add a Blotato node
2. Select Resource: "Source"
3. Select Operation: "Create"
4. Choose the source type
5. Provide the URL or text input
6. Execute the authorized extraction and retain the returned `id`.

### Get Source

1. Add another Blotato node
2. Select Resource: "Source"
3. Select Operation: "Get"
4. Pass the resolution ID from the Create step
5. Execute and inspect `status`.
6. For `queued` or `processing`, wait at least 10 seconds before another Get within a bounded wait.
7. For `completed`, use the returned `content`.
8. For `failed`, stop and read `message` from the API result.

One Wait followed by Get does not guarantee completion. The node's `_hint` text is supplementary. Inspect the operation status and error fields. A Source result does not authorize a later generation or publication.

For full API details, see [Create Source](/rest-api-reference/create-source.md).

***

## Troubleshooting

### Template shows question marks instead of the Blotato logo?

1. Enable Verified Community Nodes first
2. Install the Blotato node
3. Re-import the n8n template

### Need help?

Contact support by clicking the orange button in the bottom right corner within the Blotato app.


---

# 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-blotato-node.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.