Actions11
Overview
This node, named "Meta Publisher," enables publishing content to multiple Meta platforms including Instagram, Facebook Pages, and Threads. Specifically for the Threads resource with the Publish Carousel (Threads) operation, it allows users to publish a carousel post composed of multiple media items (images or videos) along with optional accompanying text.
Typical use cases include automating social media marketing workflows where a user wants to programmatically post multi-item carousels on Threads accounts. For example, a brand could schedule a carousel showcasing several product images or videos with descriptive text, directly from an automation workflow without manual posting.
Properties
| Name | Meaning |
|---|---|
| Input Source | Choose where the node reads its parameters from: either directly from input fields ("Fields") or from a JSON property path in the input data ("From JSON Property"). |
| JSON Property Path | Dot notation path inside the input item JSON to extract parameters when "From JSON Property" is selected. Examples: $json (whole item), data, or payload.post. |
| Polling Interval (Sec) | Interval in seconds to check the processing status of the published post. Range: 1 to 60 seconds. |
| Max Wait (Sec) | Maximum time in seconds to wait before stopping polling for the post status. Range: 30 to 3600 seconds. |
| Threads User ID | The user ID of the Threads account where the carousel will be published. This is required. |
| Items | Collection of media items to include in the carousel. Each item requires: |
| - Type | Media type of the item: "Image" or "Video". |
| - URL | URL of the media file to be included in the carousel. Required. |
| - Alt Text | Optional alternative text description for accessibility or SEO purposes. |
| Text (Optional) | Optional text caption or message to accompany the carousel post. |
Output
The node outputs JSON data representing the result of the publish operation for each input item processed. The exact structure depends on the underlying API response but generally includes identifiers and status information about the published carousel post.
If the operation involves asynchronous processing, the node polls the status at intervals until completion or timeout, then returns the final status.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with Meta's Graph API.
- The node internally uses helper functions (
n.OPS.threadsPublishCarousel) to handle the actual API calls and polling logic. - Proper configuration of the Threads User ID and valid media URLs accessible by the API are necessary.
- Network access to Meta's APIs must be available from the n8n environment.
Troubleshooting
- Invalid job payload (not an object): Occurs if the input JSON property path does not resolve to an object or array of objects. Ensure the JSON path is correct and points to valid structured data.
- No JSON found at path: Indicates the specified JSON property path does not exist in the input item. Verify the path string matches the input data structure.
- Unsupported Threads operation in payload: Happens if an invalid operation name is provided. Confirm that the operation is exactly "threadsPublishCarousel" for this use case.
- Missing required parameters: The Threads User ID and media URLs for each item are mandatory. Missing these will cause errors.
- Timeout waiting for post status: If the post processing takes longer than the Max Wait time, the node stops polling. Increase Max Wait if needed.
- API authentication errors: Check that the API key credential is correctly configured and has sufficient permissions.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions. It does not execute or simulate runtime behavior.