Automations — standing rules

Standing rules: the three trigger kinds, what rules can do, dry-run testing, and managing rules.

Open in Jordyn:/automations/chat

Automations

An automation is a standing rule: "whenever X happens, do Y." You create them by describing them in chat, and Jordyn compiles your words into a rule and shows you a flowchart of exactly what it will do before anything runs.

The three kinds (and only these three)

  1. Email-triggered — "when an email from Steve arrives, reply thanking him and flag me." Incoming mail is checked about every 30 minutes.
  2. Daily — "every morning, find clients with renewals inside 60 days and email me the list." Runs each morning, has access to your book of business, and emails you a digest of what it did. With your explicit consent, a daily rule may place phone calls — hard-limited to 5 per run, and never the same person twice within 30 days.
  3. Event-triggered — fires the instant something happens in Jordyn: a booking on your booking page, an opt-in signup, a campaign reply, or a completed phone call. Inbound webhooks from outside systems (Typeform, Stripe, Zapier) can fire rules too.

There are no hourly, weekly, or monthly schedules — Jordyn says so plainly rather than approximating.

What rules can do

Send or reply to email in Jordyn's voice, apply labels, create to-dos, read and write your connected storage, update your case ledger, place calls (daily rules only, with consent), and notify other systems. Rules can include wait steps ("wait 2 days, then follow up"). They act on your connected accounts — never on your computer.

Testing before it runs

Every new rule can be dry-run against your ~50 most recent real emails: you see exactly which messages would have matched and what the rule would have done — with zero actions taken. Enable it only after that looks right.

Managing rules

  • Ask "what automations do I have?" for the list, with run counts and last-run times.
  • Rules can be disabled (paused, kept) or deleted (gone for good).
  • Watch-style rules ("tell me when he replies") expire on their own — about 14 days out unless you name a date — so old watchers never pile up.

Automations versus campaigns

An automation reacts to something happening. An outbound sequence — "nurture Bill", "follow up until he books" — is a campaign, and Jordyn will always build it as one, because a rule that auto-replies sales copy to a person's incoming mail is the wrong tool.

Related

Can’t find it? Ask the Guide — it answers from these same articles.