Instagram

Instagram connection goes through Facebook Login, where the user selects which Instagram accounts and Facebook Pages to grant access to. Once Instagram issues the token, it is bound to the specific account selected in that OAuth flow. Composio cannot repoint that token server-side to another Instagram account. To switch accounts, reconnect and select the intended Instagram account/page in the Facebook picker.

The Instagram toolkit uses Instagram API with Business Login for Instagram. OAuth errors commonly happen when unsupported or unverified scopes are configured. Prefer the default scopes where possible, because they are intended to cover the toolkit's supported actions. If configuring custom scopes, use only Meta-supported Instagram Business Login permissions and remove unsupported scopes such as user_profile.

Instagram toolkit requires a Business/Creator account for supported business features

Instagram toolkit support is for Instagram Business/Creator account flows. If you are using a personal Instagram account, convert or connect a Business/Creator account linked through Meta/Facebook as required by Instagram's API.

Use `INSTAGRAM_LIST_ALL_MESSAGES` to fetch Instagram messages

Use INSTAGRAM_LIST_ALL_MESSAGES to list Instagram messages. In playground, select the correct auth config/connected account; if the desired connected account does not appear, initiate a new connection for the test account and use that auth config.

Instagram DM send failures with code 10/subcode 2534022 are Meta's 24-hour messaging window

That error is enforced by Instagram/Meta, not Composio. Instagram's messaging API only allows replies inside the 24-hour messaging window. Meta opens that window for specific interactions such as a direct DM from the user, story reply, story mention, or icebreaker/quick-reply button tap. Likes, comments, and follows do not open the window. If the qualifying interaction is older than 24 hours or never happened, the send will fail.

If you have a fresh qualifying inbound DM, an accepted message request, the correct Business/Creator account, and a successful INSTAGRAM_LIST_ALL_MESSAGES call, the generic 24-hour-window explanation is not sufficient. Contact Composio support with the redacted call details for further investigation.

The current INSTAGRAM_SEND_TEXT_MESSAGE action sends messaging_type: "RESPONSE" for a normal in-window reply.
INSTAGRAM_MARK_SEEN can also return the same Meta subcode. Because sender actions are more provider-limited, retest the action before assuming it is supported for every Instagram account. If it still fails, contact Composio support with the exact request or log ID.

For custom Instagram/Meta OAuth, configure the redirect URI in the Meta app

For custom Meta/Instagram OAuth apps, make sure the redirect URI is added in the correct Meta app configuration field and matches the Composio auth config redirect URI. Customers using their own auth app credentials can configure their own redirect URI.

For Instagram DMs via n8n/Claude, Connect MCP can simplify setup

For Instagram DM workflows in MCP clients, use Connect MCP at https://connect.composio.dev/mcp with the x-consumer-api-key header copied from the current AI Clients setup in the Composio dashboard. The agent can then start the Instagram connection flow when authentication is needed.

`INSTAGRAM_POST_IG_MEDIA_COMMENTS` failures can be caused by an incorrect `ig_media_id`

If INSTAGRAM_POST_IG_MEDIA_COMMENTS fails, verify the ig_media_id being passed. An incorrect media ID can cause the action to fail even when the action itself is available.

Instagram is available as a toolkit and can be connected via a new authConfig

Instagram is available in the Composio marketplace. Create a new Instagram authConfig, complete the OAuth connection for the Instagram account, and then use the Instagram toolkit tools. The authConfig ID / integration ID can be found from the dashboard.

Publish local media with `image_file` or `video_file`

For a locally generated JPEG, PNG, or video, use INSTAGRAM_POST_IG_USER_MEDIA and pass the staged file through image_file or video_file. Upload or stage the file first; a raw local path, workspace/session path, or stale storage key can fail before Meta receives the request. Follow with INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH when the create step succeeds.

Alternatively, use image_url or video_url only when it is a direct HTTP(S) media URL that Meta can fetch without authentication. The older INSTAGRAM_CREATE_MEDIA_CONTAINER path is URL-only and does not accept local files directly.

If the error says Failed to download file with s3key ... storage returned HTTP 404, re-stage the file and retry with the fresh FileUploadable object. Treat this as a Composio file-reference failure before provider execution, not an Instagram OAuth failure.

Last verified Aug 12, 2026

On this page