Skip to content
Arcane CRMArcane CRMHelp

Atlas

Answers from this help and cites its sources. 20 questions a day.

Triggers

The trigger is a workflow’s first block: it says when the workflow starts and what it receives. A workflow can have several, for example a CRM event and an e-mail reply that each lead to their own branch.

Depending on your plan Editor › palette › Triggers Every member in a draft; they only fire once the workflow is active

The list

Section titled “The list”
Trigger The workflow starts…
Schedule at a regular interval (minutes, hours, days, weeks, months) or by a cron expression, on Paris time. 5 minutes at least.
CRM event when a record of an object is created or updated, optionally only if some fields changed. What the workflow writes itself doesn’t start it again.
E-mail received when an e-mail lands in the inbox of a connected Gmail or Outlook account (not drafts, spam or sent mail), with an optional filter on the sender and the subject.
E-mail classified when Verdict, a sender rule or a person files an e-mail in a category of the Inbox. Once per e-mail and category, never for an e-mail more than 2 days old.
Calendar event a few minutes before an event of a connected account’s primary calendar, or when it is added, changed or cancelled. All-day events don’t fire “about to start”.
Meeting transcribed when a recorded meeting is transcribed and analysed.
Recording status when a meeting’s recorder enters the waiting room, starts, ends or fails.
Document signed when every signer has signed and the signed PDF is filed on the record.
Lawyer’s reply when the lawyer replies in the thread of a contract sent by the “Send to the lawyer” block.
Chat message received when a visitor writes on the customer chat, optionally only for one widget or one Verdict category.
Sequence: reply or end when a contact replies to a sequence, finishes it or leaves it (meeting, bounce, unsubscribe, removal).
Incoming webhook when an external app sends a JSON POST to the workflow’s address.
API call when an app calls the CRM’s API with an API key.
Manual launch on demand, from the editor, from a record or by asking Atlas.

Triggers tied to a mailbox, a calendar or meetings only see what the person who publishes the workflow sees: their connected accounts and the shared mailboxes they can read, their meetings, and the meetings shared with the team on a record they can read.

Incoming webhook

Section titled “Incoming webhook”
The panel of an Incoming webhook trigger: the sending app (Stripe), the webhook URL, the saved signing secret and the Listen for a test call button.

Once the workflow is saved, the panel shows the Webhook URL. The calling app authenticates:

  • with the workflow’s secret token, in the X-Arcane-Webhook-Token header;
  • or with an HMAC-SHA256 signature of the body made with that token, in the X-Arcane-Signature: sha256=<hex> header;
  • or, if you choose the Sending app (Stripe, Shopify, WooCommerce, GitHub, Calendly, Typeform, Standard Webhooks), with its own signature: paste the URL into that app and save here the Signing secret it gives you. The token is then no longer used.

Regenerate the secret token creates a new one: the old one stops working at once. The URL and the token are only visible to administrators and to the workflow’s Automator author.

Listen for a test call waits 10 minutes for a call: send something from your app, the CRM keeps the body it received and offers its fields in the expression autocomplete ({{ $json.body.… }}). While listening, the call doesn’t start the workflow if it isn’t active. Map the fields with Atlas asks it how to connect those fields to the CRM’s.

API call

Section titled “API call”

The app calls POST /v1/workflows/<id>/run with an organization API key that has the “Run workflows” permission (Settings › Integrations › API keys), the header Authorization: Bearer <key> and a JSON body. The workflow must be active. The call waits at most 30 seconds for the workflow to finish and receives what the Reply to the call block returns; after that, it receives the run’s id.

Manual launch

Section titled “Manual launch”

With no object chosen, the workflow is started with Run now in the editor (administrators and Automator author), or by asking Atlas.

With an object (for example Opportunities), once the workflow is active, every record of that object shows a Run a workflow button: the workflow receives the record. Any member can start it; a Workflow started message offers to Follow the run.