Actions & Messages

Choose what a flow does: internal notifications, webhooks, email, and SMS.

Actions define what a flow actually does.


Built-In Actions

Notification

Sends internal notifications inside TatTool.

  • Used for staff/admin communication
  • Good for “new booking created” alerts or internal reminders

Webhook

Sends structured data to an external system.

  • Useful for integrations and custom automation
  • Typical use cases: syncing events, triggering external workflows, notifying other systems

Message Actions (Email / SMS)

Flows can send messages by email or SMS:

  • Send Email – sends email through the provider selected in SettingsCommunication
  • Twilio SMS – sends SMS messages

See:

Recipients need contact details

Email and SMS actions require that the recipient has an email address or phone number available (for example the client or participant).

Email provider selection

The Send Email node is provider-neutral. If your organization selects TatTool Email Provider, emails use TatTool-managed sending. If your organization installs and selects Resend, the same email node sends through Resend.


Recipients

Recipients may include:

  • Client
  • Participant (artist)
  • Organizer
  • Admins

Which recipients are available depends on the trigger type and the action.


Email Logs

Open the related booking/payment/consent form → Flow Logs to see whether an email node ran, which provider was used, and any error message returned during sending.


Message Variables

Message-based actions support variables using double curly brackets.

Example:

Hello {{client_name}}

Variables are replaced with real values when the message is sent. Available variables depend on the trigger type (booking, payment, consent form, etc.).

Use the variable picker

When editing a message/subject, use the variable picker in the flow editor to see what’s available for the selected trigger.