Delete Post
twitter.delete_post
ActionChat & messagingconnection required
Calls the X (Twitter) API with the connection's credentials.
Delete one of the authenticated user's own posts.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- X (Twitter)
- Secret shape
- the X OAuth2 user-context access token, or {"access_token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
tweet_id Numeric id of the post, e.g. the 'id' twitter.create_post emitted. Supports {{ }}. | string | Yes | — | — | 1460323737035677698 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"tweet_id": "1460323737035677698"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
deleted True when X confirmed the deletion. | boolean | — |
tweet_id The post that was deleted. | string | — |
{
"deleted": false,
"tweet_id": ""
}Notes
- X API access is tiered and metered: most read endpoints need a paid plan, and since 6 February 2026 new developers get pay-per-use credits rather than a free tier. A 403 here usually means the plan, not the code.
- The connection's access token must already carry the scopes this node needs; X does not grant them per call, so a missing scope is a 401 on every run.
- Needs the OAuth2 scopes tweet.write, tweet.read, users.read.
- A post that is already gone answers 404, which fails the step rather than reporting deleted=false.
See Delete Post run in a workflow.
In a technical demo we add the X (Twitter) connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.