Tailflow
Log inStart free
Skip to article
Browse documentation

Actions

Choose an action

Compare notifications, data shaping, required connections, and availability.

Notify

Slack posts to a channel using a Slack connection. Email sends to one recipient from Tailflow. Webhook sends the event and earlier outputs to a public URL. Post to X publishes text using your X connection.

Action Picker and Email Configuration
Add action · Notify
SlackChannel message
EmailEmail message
WebhookJSON request
Post to XText post
Email
Example. Choose a notification from the action picker, then fill in its inspector fields.Changes stay in this example. Nothing is saved or sent.

Shape

Agent uses your connected model to produce text about the event. Transform runs a script over the available input. Decode interprets encoded contract data with an ABI. NFT metadata retrieves descriptive fields for an NFT Transfer event.

Place a shaping action before the message that uses its result. Outputs are local to the path, and a shape action does not itself change the original event.

Transform Action Configuration
Path 1
Every event
Transform
Selected action
1Transform
Sample output
actions.transform_1.summary
125000 tokens moved
Continue on error
A failure stops later actions on this path.
Example. Read the event through input.event and return an object. A test executes the script and lets you inspect the fields it returns.Changes stay in this example. Nothing is saved or sent.

Not available yet

Token price as an action, Linear issue creation, and Google Sheets row creation are not available in this version. A visible connection or dimmed picker item does not mean the action can run.

Check failures and cost

Every action has a result in Runs. Failed actions stop their path by default. Review Continue on error before deciding to allow later steps to proceed.

Completed actions consume credits: Slack, Email, Webhook, Post to X, Decode, and NFT metadata use 1 each; Transform uses 2; Agent uses 2. Test runs do not use Tailflow credits.

Continue on Error and Path Outcomes
Transform
Run · Path 1
TransformFailed
EmailSkipped
With Continue on error off, the failed action stops later actions on this path.
Example. Select the action to change Continue on error. Keep it off when later actions require its result.Changes stay in this example. Nothing is saved or sent.