Tailflow
Log inStart free
Skip to article
Browse documentation

Start here

Build your first flow

Create a token transfer alert, preview its message, and enable it for future events.

What you will build

A flow watches for an event and runs the actions you choose. This walkthrough sends an email when a transfer of a selected token meets your minimum amount. You do not need to connect a wallet or write code.

Flow Designer
Example flow: Disabled
Email
Continue on error
A failure stops later actions on this path.
Example. A matching transfer enters the path, then runs Email. Select a card in the designer to edit its settings.Changes stay in this example. Nothing is saved or sent.

Choose a trigger

Open Flows and select New flow. Give it a name that describes the alert, such as “Large USDC transfers”. You can also start from a source in Sources.

  1. Choose Token Transfer (ERC20).
  2. Select the chains you want to watch, then choose a token. Check its address and chain rather than relying on the symbol alone.
  3. Add a Value filter with ≥ and an amount such as 100000. Value is in token units; Value (USD) is an indicative dollar estimate.
  4. Inspect Example triggers and select a row to review its fields. These are matching examples from the last day, not notifications already sent by your flow.
Token Transfer Trigger Configuration
1Event source
Token Transfer (ERC20)
2Filters
Edit the conditions to explore the controls. Event samples stay fixed.
Inspect Example triggers to check your selection.
3Trigger
Chains
1 selected · 3 of 7 chains shown
Fires
Event shape
token_symbol
USDC
value_decimal
125000
from_address
0x1111111111111111111111111111111111111111
Example. Choose the event source, then narrow it with a Value filter. Chains are selected in the trigger inspector.Changes stay in this example. Nothing is saved or sent.

Add an email

In the designer, use a path with no condition to act on every event admitted by your trigger. Add Email and fill in To, Subject, and Body. Email sends from Tailflow; no email connection is needed.

  1. Set To to your email address.
  2. Use the event field picker to insert values in the message.
  3. Wait for your changes to save before testing.
Email Action Configuration
Path 1
Every event
Email
Selected action
1Email
Continue on error
A failure stops later actions on this path.
Example. Select Email on the canvas to open this inspector. Use the event’s field paths in Subject and Body; To identifies the recipient.Changes stay in this example. Nothing is saved or sent.
Message template
{{ event.token_symbol }} transfer
Amount: {{ event.value_decimal }}
From: {{ event.from_address }}
To: {{ event.to_address }}
{{ event.explorer_tx_url }}

Test, then enable

Select Test run. Review the rendered recipient, subject, and body, and fix missing fields or failed steps. A test does not send the email.

The trigger must have matched an example before you can enable the flow. If none appear, check your chain, token, and filters or wait for matching activity.

Select Enable flow when ready. The flow watches future events; enabling does not replay the examples. Open Runs or Activity after a new matching event to check the result.

Email Test Run Preview
Test runDry
Path 1 · Every eventMatched
Email
ops@example.comWould send
Subject
USDC transfer
Body
125000 tokens moved
Nothing is sent during this test.
Example. A dry test shows which path matches and what Email would send. “Would send” is a preview, not a delivery confirmation.Changes stay in this example. Nothing is saved or sent.