Build your first automation

GuidesDraft — not publishedUpdated 2026-07-26

Automations are trigger → condition → action. Keep each flow single-purpose; three small flows are easier to debug than one branching monster.

  1. Pick a trigger — inbound message, keyword, form submission, tag change or schedule.
  2. Add conditions — channel, contact attribute, consent state, business hours.
  3. Add actions — send a template, assign a team, set an attribute, call a webhook.
  4. Test in draft against a test contact.
  5. Publish and watch the run log for the first day.

Common first automations

  • Out-of-hours acknowledgement with expected response time.
  • Keyword routing: BILLING to finance, HELP to support.
  • Escalation when a conversation has been unanswered past your SLA.

Steps at a glance

  1. Pick a triggerChoose what starts the flow: inbound message, keyword, form submission, tag change or schedule.
  2. Add conditionsFilter on channel, contact attribute, consent state or business hours.
  3. Add actionsReply with a template, assign to a team, set an attribute, or call a webhook.
  4. Test in draftRun the flow against a test contact before publishing.
  5. Publish and monitorPublish, then watch the run log for the first day of live traffic.
Next step

Bring this to your enterprise stack

See how a dedicated Arino One instance — deployed in your region (EU, NA or APAC) — would sit inside your operation. Architecture, DPA, and rollout plan walked through live.