Where. Pipeline → Automations (/admin/automations). Start from a recipe — thank strong applicants, nudge me about people waiting a week, move my Yays to Reviewing, celebrate hires in Slack, send new applicants to another system, close out after 30 days, a morning summary, catch a webhook — or a blank one. They belong to your organization: everyone on your team sees and edits the same ones.
Triggers (what starts a run): someone applies; an applicant moves stage (to or from the stages you pick — on the board, in a list, in Swipe review or by another automation); you rate someone in Swipe review; an applicant has waited N days in a stage (once per stay — the builder says how many are waiting that long already before you switch it on); a schedule (every hour, day, weekday or week, UTC, with a summary of your pipeline); a webhook arrives (any app that can POST to a URL); sourcing finds new matches. Most can be limited to some of your jobs.
Steps, top to bottom: Only continue if… (conditions on anything the run knows — match score, stage, rating, the job, their e-mail, a webhook's fields, an API's answer — all of them or any); Wait (minutes to 30 days); Move to a stage (their stage e-mail goes with it, once per stage, exactly as on the board); E-mail the applicant (from your company's name; counts as one of your e-mails); Notify a teammate (free — it isn't outreach); Add a note; Add to a folder; Send a webhook (signed JSON); Call an API (any method, headers and JSON body; later steps can use the answer); Post to Slack or Microsoft Teams (their incoming-webhook URLs).
Building. Search the steps on the left and drag one into the flow (or click it); drag steps by their card to reorder, or use ↑ ↓. Text fields take merge fields — Insert a field lists what this trigger's runs know, e.g. {{candidate.first_name}}, with a fallback: {{candidate.first_name | there}}. A JSON body is read as JSON, so a field always lands as a proper value. Problems show on the step they belong to; it switches on once there are none. Test runs it once on a real applicant (or an example webhook body): e-mails go to you, moves, notes and folders are only described, webhooks and API calls are real.
Other apps. API keys go in Secrets on the Automations page — {{secret.NAME}} in a URL, header or body. They're encrypted, never shown again (only their last four characters), and never go into e-mails or the run history. Calls go only to https addresses on the public internet, with a 10-second limit, at most 60 a minute for your organization; a call that fails for a passing reason (a timeout, a 5xx, a 429) is tried again after 1, 5 and 30 minutes. Each webhook carries X-Amberrole-Signature (an HMAC-SHA256 of "timestamp.body" with the automation's signing secret, shown in the step) so the other end can check it came from you. A webhook automation gets its own inbound URL — shown once; keep it private, and make a new one if it leaks.
Runs. Under the builder, every run with what each step did; a failed run can be tried again from the step that failed. Runs keep what they did for 90 days; after that only whether they worked. An automation never sets itself off, chains of automations stop three deep, and each automation starts at most 500 runs an hour.
Posting and reviewing are free. Every stage, e-mail and export described here is in the console from the first sign-in.