Gorilla Dash

Help Centre

Guides for every part of Gorilla Dash

Step-by-step how-to guides written by the team that builds the product. Read them here, or download any guide as a PDF.

Sending Steps

Email steps

Download PDF

Sending an email from a workflow, choosing the template, and writing for an automated sequence.

Last updated September 2, 2026


An email step sends one of your existing emails. Build and test it in email marketing first — the workflow chooses it, it does not write it.

Choosing the email

Search your emails and pick one. Where a workflow runs for tribes, a template for tribes can be used so each tribe sends its own version.

Writing for an automation

  • Do not date it. "Our spring offer" is wrong by June; an automation runs for years.
  • Do not reference the trigger too precisely. "You enquired yesterday" is wrong the moment somebody is enrolled by a backfill.
  • Write it as one person to another. The best automated emails read like a short personal note, not a newsletter.
  • One action. A sequence gets several chances; each email needs only one ask.

Check it in the sequence, not on its own

READ THE WHOLE SEQUENCE IN ORDER
Each email may be fine and the set still wrong — three messages that all open the same way, or a second that assumes they read the first. Read them together as a customer would receive them.

Who is excluded

The same exclusions as any marketing email: unsubscribed, bounced, and anybody with marketing emails switched off on their contact. An automation cannot get around an unsubscribe, and should not.

Next · Sending StepsSMS steps