> 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/make.com.md).

# Make.com

Connect Blotato in Make, verify account access, and branch on source, visual, and publishing results.

Use Blotato modules in Make for operations exposed by your installed integration. For an operation or field absent from a module, use Make's HTTP module with the [REST contract](/rest-api-reference/api-reference.md). MCP tool arguments are not Make module fields or REST bodies.

## Connect and verify

1. Connect the intended social accounts in [Accounts](https://my.blotato.com/accounts).
2. Read [Authentication](/api-and-mcp-concepts/authentication.md) before generating an API key. Generating a key during a free trial starts paid access.
3. Add a Blotato module to a Make scenario.
4. Configure its connection with your Blotato API key in the credential field, not in chat or workflow text.
5. Refresh the available accounts and select the intended platform and destination.

To verify through an HTTP request, use the same Blotato credential with this read-only request:

```http
GET /v2/users/me/accounts HTTP/1.1
Host: backend.blotato.com
blotato-api-key: YOUR_API_KEY
```

A response containing `items` verifies access. An empty array means no accounts were returned, not an authentication failure. Do not create a test post to diagnose an empty account list. Follow [Account lookup](/api-and-mcp-concepts/accounts-and-identifiers.md).

## Choose an operation

| Task                | Contract and completion check                                                                                                                                                |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Publish or schedule | [Publish a post](/agent-workflows/agent-workflows/publish.md) and [Schedule](/agent-workflows/agent-workflows/schedule.md). Retain `postSubmissionId` and verify the result. |
| Prepare media       | [Media uploads](/api-and-mcp-concepts/media-uploads-and-conversion.md). Public media URLs go directly into `mediaUrls`.                                                      |
| Generate a visual   | [Create a visual](/agent-workflows/agent-workflows/visuals.md). Retain the visual ID and verify output before publishing.                                                    |
| Extract a source    | [Extract content](/agent-workflows/agent-workflows/sources.md). Retain the source ID and wait for completed content.                                                         |

Do not assume an operation exists in Make because it exists in n8n or MCP. Inspect the installed module before choosing an HTTP fallback.

## Using Source Modules

### Supported Source Types

REST supports `text`, `article`, `youtube`, `twitter`, `tiktok`, `perplexity-query`, `audio`, and `pdf`. The source type is required in a REST request.

If your Make module provides a URL choice with type inference, inspect the resulting request when extraction fails. `url` is not itself a REST `sourceType`. Follow [Create Source](/rest-api-reference/create-source.md) for the request body.

### Create Source

1. Select the source-creation operation exposed by the installed module.
2. Supply the source URL or text.
3. Run the authorized extraction.
4. Retain the returned source ID. In REST, this is `id`.

### Get Source

1. Pass the saved ID to the source-status operation or `GET /v2/source-resolutions-v3/{id}`.
2. Read `status`.
3. For `queued` or `processing`, wait at least 10 seconds before another check within a bounded wait.
4. For `completed`, use the returned `content`.
5. For `failed`, stop and read `message` from the REST result.

One Sleep followed by Get does not guarantee completion. Do not start another extraction because the first result is unfinished.

## Using Visual Modules

### Create Visual

1. [Inspect the selected template's inputs](/rest-api-reference/create-video.md#inspect-inputs-without-generating-a-visual).
2. Supply the template's complete ID and matching inputs.
3. Set `render: true` when the requested result requires exported media.
4. Run the authorized generation.
5. Retain its creation ID. In REST, this is `item.id`.

A template lookup does not require a generation job. Do not submit a blank job to learn field names.

### Get Visual

1. Pass the saved ID to the visual-status operation or `GET /v2/videos/creations/{id}`.
2. Inspect the result before publishing. REST wraps these fields in `item`. Compare module output with the [response contract](/rest-api-reference/create-video/find-video.md) rather than assuming its field layout.

| Result                                                     | Next action                                                             |
| ---------------------------------------------------------- | ----------------------------------------------------------------------- |
| `error` is present, even with `script-ready`               | Stop and report the error.                                              |
| `creation-from-template-failed` or `insufficient-credits`  | Stop. Diagnose before another authorized paid attempt.                  |
| `draft`                                                    | Report a draft, not an exported visual.                                 |
| `done` with the required media                             | Use `mediaUrl` for video or `imageUrls` for images.                     |
| A known processing state without an error                  | Wait at least 15 seconds, then check the same ID within a bounded wait. |
| An unrecognized state or `done` without the required media | Retain the ID and result for diagnosis. Do not recreate automatically.  |

### Scenario Pattern

1. Create the source or visual only when required for the requested task.
2. Wait for its operation-specific interval.
3. Retrieve its status.
4. Branch on the result. Loop only for an unfinished job within the waiting limit.
5. Continue with completed output.
6. Publish only when the user authorized publication.
7. Verify the publication before marking the scenario's content as posted.

Elapsed time does not prove completion. A failed status lookup is not permission to repeat a write. Follow [Publishing status](/start-with-an-ai-agent/publishing-status.md).

For website video creation, use [Videos > New](https://my.blotato.com/videos/new). The in-app AI Agent's video restriction does not restrict external Make or REST visual generation.


---

# 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 dynamically 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/make.com.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 `build a script that syncs our docs to a CMS` 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.