Category: Automations

ORCHESTRIS support articles for Automations.

  • How do I create an automation?

    How do I create an automation?

    How do I create an automation?

    Short answer

    Create automations from the Automations area of the CRM board you want the rule to watch, then build the rule as a sentence using a trigger and an action.

    Where to start

    • Open the CRM board that should run the automation.
    • Choose Automations, then choose Create Automation.
    • The automation belongs to that board unless you choose an action that moves or connects the item to another board.

    Build the sentence

    • Choose the trigger first, such as a status changing, a row moving groups, a form submission arriving, or a date being reached.
    • Choose the action next, such as moving the item to another group, sending an email, creating a workspace, preparing a document, or updating another column.

    Before turning it on

    • Confirm the column, group, board, and email template selections are correct.
    • Use a test lead before relying on the automation for a real client workflow.
    • If the automation references a column, ORCHESTRIS should keep using the stable system key even if the visible column name changes later.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do CRM and campaigns connect?

    How do CRM and campaigns connect?

    How do CRM and campaigns connect?

    Short answer

    CRM data should help campaigns know who to contact, what event or lead data to use, and which workflow stage should trigger communication.

    CRM source data

    • Lead name
    • Email address
    • Event type
    • Event date
    • Status or group
    • Assigned owner
    • Package or service interest

    Useful campaign triggers

    • When a lead submits a form
    • When a lead moves to a specific group
    • When an event is created
    • When an event date is approaching
    • When a planning item needs attention

    Safety checks

    • Campaigns should preview recipients before sending.
    • Email templates should be reviewed before being automated.
    • Do not send test emails to real clients unless the campaign is clearly ready.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How can an automation create a workspace and send a magic link?

    How can an automation create a workspace and send a magic link?

    How can an automation create a workspace and send a magic link?

    Short answer

    Owner CRM automations can be designed so an approved prospect creates a workspace account, then sends the admin a magic login link using mapped CRM fields.

    Typical trigger

    • Use a status or group change such as Approved as the trigger.
    • Map the workspace name from the CRM column that holds the company or account name.
    • Map the admin email from the CRM column that should receive the login link.

    Typical actions

    • Create the workspace account.
    • Create or assign the workspace admin user.
    • Send an email template that contains the generated workspace magic link.

    Safety checks

    • Use stable column keys behind the scenes so renaming a column does not break the automation.
    • Keep email templates editable so the owner team can adjust onboarding language without changing code.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do CRM automations work?

    How do CRM automations work?

    How do CRM automations work?

    Short answer

    CRM automations watch for a trigger, such as a status or group change, then run an action like moving an item, sending an email, creating a workspace, or preparing a contract workflow.

    Automation sentence builder

    • Automations should read like a sentence: when this happens, then do that.
    • Each blank in the sentence opens the correct selector for boards, groups, columns, email templates, or contract categories.

    Stable column keys

    • Changing a visible column name should not break automations because automations should reference the stable system key behind the column.

    Useful starting automations

    • When a lead moves to Booked, move it to an event or client workflow.
    • When a platform prospect changes to Approved, create a workspace and send the admin magic login link.
    • When a contract is needed, prepare a document from the right template category using mapped CRM data.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.