Overview
This node allows users to interact with Instagram Direct Messages (DMs) through the Meta Graph API. Specifically, the "Get Conversation" operation retrieves detailed information about a particular Instagram DM conversation by its ID. This is useful for scenarios where you want to fetch the full details of a conversation, including participants, messages, and timestamps, for analysis, monitoring, or integration with other systems.
Practical examples include:
- Fetching conversation history to display in a custom dashboard.
- Archiving message threads for customer support records.
- Triggering workflows based on conversation content or updates.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of the Instagram DM conversation to retrieve. |
| Additional Options | Optional parameters to customize the request. Currently supports: - Fields: Comma-separated list of fields to include in the response (default: id,participants,messages,updated_time). |
Output
The output is a JSON object representing the requested conversation details from Instagram's Graph API. It typically includes:
id: The conversation ID.participants: List of users involved in the conversation.messages: Array of messages exchanged in the conversation.updated_time: Timestamp of the last update to the conversation.
The exact structure depends on the fields requested via the "Fields" option.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for Instagram DM access via the Meta Graph API.
- The node uses the base URL
https://graph.facebook.com/v19.0. - Proper permissions must be granted to the API token to read Instagram conversations.
Troubleshooting
- Missing or invalid Conversation ID: Ensure the Conversation ID is correctly provided and corresponds to an existing conversation accessible by the authenticated account.
- Permission errors: If the API returns permission denied errors, verify that the API token has the necessary scopes to read Instagram DMs.
- Invalid fields parameter: Providing unsupported field names in the "Fields" option may cause API errors. Use only valid field names as per the Meta Graph API documentation.
- Network or API errors: Temporary network issues or API rate limits can cause failures. Implement retry logic or check API usage quotas.
Common error messages are returned as JSON with an error property containing the message, which the node surfaces if "Continue On Fail" is enabled.