# X: Get Events

Retrieve supported X automation events. Delivery and polling behavior depend on your connected account and provider plan; provider charges can apply.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## When to use this node

Retrieve supported X automation events. Delivery and polling behavior depend on your connected account and provider plan; provider charges can apply.

Add **X: Get Events** to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

## Before you begin

Connect X in **App Connections** first. Select the intended account in this node; an account connected to a different service is not interchangeable. Available actions depend on the permissions granted to that connection.

## Configure the fields

| Field | What to enter |
| --- | --- |
| **X Automation Account** | Connected X Automation account (configured with polling or webhooks) |
| **Event Type Filter (Optional)** | Filter by specific event type (e.g., 'tweet_created', 'tweet_mentioned'). Leave empty for all types. |
| **Limit (Optional)** | Number of events to retrieve (default: 10, max: 100)<br>Example/default shown in the editor: `10`. |
| **Force Poll Now** | Force poll X API immediately, ignoring polling interval (provider charges can apply). Use 'true' to force poll, 'false' to respect interval.<br>Choices: `false`, `true`.<br>Example/default shown in the editor: `false`. |

## Use the result

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

| Output | Meaning / label |
| --- | --- |
| `result` | Result Message |
| `eventCount` | Event Count |
| `newEventCount` | New Events Count |
| `polled` | Polled X API (yes/no) |
| `pollCost` | Poll Cost ($) |
| `forwardedToWebhook` | Forwarded to Webhook (yes/no) |
| `lastPolledAt` | Last Polled At |
| `events` | Events (JSON Array) |
| `firstEventId` | First Event ID |
| `firstEventType` | First Event Type |
| `firstEventText` | First Event Text |
| `firstEventTimestamp` | First Event Timestamp |
| `firstEventSenderId` | First Event Sender ID |
| `firstEventSenderName` | First Event Sender Name |

## Connect the next step

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

## Test it in a workflow

1. Configure this node with a small, recognizable test input or a test resource.
2. Check the variables from preceding steps and the connection selected in the inspector.
3. Save the workflow. For event-driven flows, generate the actual event; use **Run** only for a Manual workflow.
4. Open **Workflow Activity** and check the outcome before enabling wider use.

## If something goes wrong

- Reconnect the account if authorization has expired, then verify its permissions on the specific resource.
- Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
- Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
- Follow the [troubleshooting guide](/help/troubleshooting/) for a symptom-by-symptom checklist.

## Related guides

- [Work with variables](/workflows/variables/)
- [Understand branches and error handling](/workflows/branches/)
- [Browse all nodes](/reference/nodes/)
- [X: Delete Tweet](/nodes/x-deletetweet/)
- [X: Get Home Timeline](/nodes/x-gethometimeline/)
- [X: Get User Profile](/nodes/x-getuserprofile/)
- [X: Get User Tweets](/nodes/x-getusertweets/)
- [X: Like Tweet](/nodes/x-liketweet/)


## Catalog coverage

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.