Actions74
- Lists Actions
- Tweets Actions
- Users Actions
- Timelines Actions
- Media Actions
- Spaces Actions
- Direct Messages Actions
- Analytics Actions
- Compliance Actions
Overview
This node integrates with the X (Twitter) API v2 via a third-party service to perform various Twitter-related operations. Specifically, for the Compliance resource and the Register Webhook operation, it allows users to register a webhook URL to receive real-time notifications about specific Twitter events related to compliance monitoring.
Typical use cases include:
- Automatically receiving updates when tweets are created or deleted.
- Monitoring user profile updates.
- Tracking direct messages for compliance purposes.
For example, a compliance team could use this node to register a webhook that listens for "Tweet Create" and "Tweet Delete" events in a premium environment, enabling automated workflows that respond to these events immediately.
Properties
| Name | Meaning |
|---|---|
| Environment | Premium environment label identifying the Twitter environment where the webhook is registered. |
| Webhook URL | The URL endpoint where Twitter will send event notifications (webhook callback URL). |
| Webhook Events | List of Twitter events to listen for. Options: Tweet Create, Tweet Delete, User Update, Direct Message. |
Output
The node outputs an array of JSON objects, each representing the response from the Twitter API after attempting to register the webhook. Each output item corresponds to one input item processed.
The json field contains the API response data confirming the webhook registration details or any relevant metadata returned by the Twitter compliance API.
If errors occur and the node is configured to continue on failure, error details are included in the output as JSON objects with an error message field.
No binary data output is produced by this operation.
Dependencies
- Requires an active subscription and valid API key for the third-party service that proxies Twitter API calls.
- Requires configuration of credentials within n8n for accessing this third-party API.
- The node internally uses a helper class to interact with the Twitter API v2 endpoints.
- The webhook URL must be publicly accessible to receive incoming HTTP requests from Twitter.
Troubleshooting
- Invalid subscription or API key: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly set up and has the necessary permissions.
- Webhook URL unreachable: Ensure the provided webhook URL is reachable from the internet and can accept POST requests.
- Event selection issues: Confirm that at least one valid event type is selected; otherwise, the registration may fail.
- API rate limits or permission errors: These may occur if the Twitter account or environment does not have access to compliance APIs or exceeds usage quotas.