Accounts and identifiers

Select current account and destination IDs and distinguish submissions, posts, schedules, comments, and messages.

Get IDs from Blotato responses. A username, profile URL, or native platform post ID does not replace a Blotato ID.

Select an account

1. Call blotato_list_accounts through MCP, or GET /v2/users/me/accounts through REST.

2. Match the returned platform and account name to the user's intended destination.

3. Use the returned account id as accountId.

4. Select any required Page, board, or playlist from the lookups below.

If several accounts match, ask which account to use. If none match, direct the user to Accounts.

After disconnecting and reconnecting an account, retrieve the current ID before retrying. A saved workflow or brand mapping might contain a stale ID. Confirm the account belongs to the same authenticated Blotato user and platform as the request.

Destination	Identifier	Where to get it
Facebook Page	pageId, required	MCP account subaccounts, or REST GET /v2/users/me/accounts/:accountId/subaccounts
LinkedIn company Page	pageId, required for this destination	MCP account subaccounts, or the REST subaccounts endpoint
LinkedIn personal profile	Omit pageId	Use the LinkedIn accountId
Pinterest board	boardId, required	blotato_list_pinterest_boards, or GET /v2/social/pinterest/boards?accountId=...
YouTube playlist	playlistIds, optional	MCP account subaccounts, or the REST subaccounts endpoint

A returned Facebook Page is a destination to select, not permission to publish to the first Page in the list. LinkedIn Page IDs apply only when the user chooses a company Page. Omitting pageId selects the LinkedIn personal profile, not a company Page. Omit YouTube playlistIds unless playlist placement is requested.

MCP's requiredFields includes hints, not the customer's destination selection. Match the requested Page against subaccounts. An empty subaccount list does not prove the platform account has no Pages, since lookup failures also need investigation. Stop if a required destination ID is unavailable.

Account not found

This error means the submitted ID did not match an account for the authenticated Blotato user and requested platform. It does not establish which value is wrong.

1. Read the failed request's accountId, content.platform, and target.targetType.

2. Retrieve accounts using the same credential or MCP connection used for publishing.

3. Select the returned account for the user's intended platform and destination.

4. Retrieve a separate Page ID when required. Do not put a Page ID in accountId.

5. Update the saved workflow mapping if it contains an old ID.

Different credentials, an ID from another platform, a Page ID used as an account ID, and an ID saved before reconnection are separate checks. An account dropdown reduces manual copying but does not guarantee a saved selection is current. An AI assistant must perform the lookup rather than assume it happened automatically.

Reconnect only when the connection state or returned error calls for it. If the same ID, platform, and authenticated user still produce the error after a fresh lookup, retain the request details and escalate. Do not assert a key mismatch without checking it. Never include keys or tokens in an escalation.

Before sending another publish request, verify the earlier submission's outcome through Publishing status.

Keep post IDs separate

ID	Use
postSubmissionId from create-post	Poll publishing status with blotato_get_post_status or GET /v2/posts/:postSubmissionId
Published post ID from post listings	Fetch analytics or comments for the published post
Scheduled post id from schedule listings	Get, update, or cancel the scheduled post
Source id	Check source extraction
Visual item.id	Check visual generation
Comment id	Fetch the comment or check reply completion
Conversation or message id	Fetch the corresponding conversation or message
Automation flow and trigger IDs	Manage the automation or a trigger

For blotato_list_posts, inspect each item's state. A scheduled item and a published item describe different records. Read the List Posts response before passing an ID to another operation.

Updating an automation's content or triggers reissues its trigger IDs. Read the returned triggers before updating a trigger. See DM automations.

Full lookup shapes: Accounts, Scheduled posts, Comments, and Messages.