Skip to main content
Each client carries variables, such as its Microsoft tenant ID or PSA client ID, that forms and workflows use to act for the right business.

Clients and variables: adding a client, giving it variables and finding your org variables (1:20).

The Clients page with Refresh, Standard Variables and New Client buttons, the Standard Variables menu open on Set Client Variables and Define Standard Variables, and a table listing Acme Corp, Initech and Globex, each Cloud Only with No agents.

​
Add a client

1

Create it

In Clients, click New Client, enter the name, choose the Environment and click Create Client.
The Create New Client dialog with the name Acme Corp, Environment set to Cloud Only, and Cancel and Create Client buttons.
2

Open it

Click View on its row. Edit changes the name or environment; Agent Credentials sets up the desktop agent.
The Acme Corp client page with Edit, Agent Credentials and Refresh buttons, a Client Details card showing the name, ID, Cloud Only environment and created date, and a Variables card with Manage Variables listing primaryContactEmail, connectwiseId, googleWorkspaceDomain and microsoftTenantId.
Choose Cloud Only for Microsoft 365-only clients; the other environments are for clients with on-premises Active Directory. Clients are shared with Triggr Core, so clients added or imported there appear here too.

​
Give it variables

1

Open its variables

Click Manage Variables on the client’s Variables card.
2

Add a variable

Click New Variable, enter the Key and Value, and click Create Variable.
The New Variable dialog with Key microsoftTenantId and Value 11111111-2222-3333-4444-555555555555, and Cancel and Create Variable buttons.
3

Fill in anything Not Set

Click Set Value on any standard variable marked Not Set.
The Acme Corp - Variables page with the Unset Variables switch on, four set variables with Edit and Delete buttons, and Default usage location (defaultUsageLocation) marked Not Set with its description and a Set Value button.
Keys are case-sensitive: microsoftTenantId works, MicrosoftTenantID doesn’t. A value that’s a number, true, false or JSON reaches workflows as that type; anything else is text. Integration IDs come from mapping instead: map clients on an integration’s Client Mapping card, or click Map or Edit Mapping on the client’s Integrations card, and Triggr saves each match as a variable.
The client's Integrations card listing ConnectWise Manage as Ready, Base config and Mapped with Edit Mapping, and Microsoft Exchange and Microsoft Graph (SAM) as Ready, Base config, mapping N/A, each with Configure.

​
Variables Triggr uses

Other Client Mapping cards save an ID for your workflows to pass into that integration’s actions: autoElevateCompanyId, auvikTenantId, dattoBcdrOrganizationId, dattoSaasProtectionId, dattoSiteId and dattoSiteUid, duoAccountId, fieldEffectOrganizationId, hubspotId, huduId, huntressId, itGlueId, ncentralCustomerId, ninjaId, organizationId (DNSFilter), sentinelOneSiteId and syncroId. Each integration’s guide says which actions take it.

​
Use variables in a workflow

Once a Client step such as Set Client From Form has run, ctx.client holds the client’s id, name, environment and every variable; org variables are in ctx.org:
environment is cloudOnly, onPremOnly, cloudAndOnPremSeparate or cloudAndOnPremSynced. A client mapped to several external clients has the first ID in haloId, all of them in haloIdList and a comma-separated list in haloIdCsv; the same goes for every mapping. See Expressions for everything else a template can read. To save a value back, add the Triggr group’s Set Client Variable step with Client ID {{ ctx.client.id }}. An empty Value deletes the variable.
The Triggr Set Client Variable step panel with Client ID ctx.client.id, Property lastNewStarterDate and Value ctx.params.startDate, each as a template.
To find a client from an ID another system sends, use Search For Client with Property Variable (see Steps).

​
Standard variables

Standard variables are the checklist of variables every client should have. They don’t hold values: a client without one shows Not Set, and a template that reads it fails with “Missing or invalid variable”.
1

Define them

In Clients, click Standard Variables > Define Standard Variables, then New Variable. Enter the Key, Label and Description, and click Create Variable.
The New Standard Client Variable dialog with Key defaultUsageLocation, Label Default usage location, and Description Two-letter country code for new Microsoft 365 users, such as GB.
The Standard Client Variables page listing defaultUsageLocation and primaryContactEmail with their labels, descriptions, created dates, and Edit and Delete buttons.
2

Fill them in for every client

Click Standard Variables > Set Client Variables. Type in a cell and press Enter to save; Esc cancels.
The Set Variables for All Clients grid with a row for each of Acme Corp, Globex and Initech and a column for Default usage location and Primary contact email; Globex has US and it@globex.com, Acme Corp has only jane.doe@acme.com.

​
Org variables

Org variables apply to your whole organisation. Find them in Settings > Org Variables; workflows read them as ctx.org.<key>, and form fields can show or hide on them.
The Organization Variables page with Setup Wizard, Refresh and New Variable buttons, listing defaultMicrosoftConnection set to microsoftGDAP, defaultPSA set to halo and helpdeskEmail set to helpdesk@yourmsp.com, each with Edit and Delete.
Setup Wizard sets the two that steps rely on. Each choice saves as soon as you click it.
1

Preferred Microsoft Connection Method

The Setup Wizard's Preferred Microsoft Connection Method question with three cards: CIPP, GDAP and Individual Enterprise Apps, the last one selected.
2

Preferred PSA

Pick your PSA and click Finish.
The Setup Wizard's Preferred PSA question with cards for Halo PSA, ConnectWise PSA, Syncro PSA, Autotask by Datto and Other.
Triggr Core’s PSA and Microsoft settings save the same two variables, so changing them in either app changes both.

​
FAQ

The client may already have a variable with that key. Click Edit on its row instead.
Create Ticket needs defaultPSA set to halo, connectwise or autotask. Run Setup Wizard and pick your PSA.
Run Setup Wizard and choose a Microsoft connection method, or set the step’s Connection Type.
The run’s client has no microsoftTenantId. Add it on Manage Variables.
ctx.client is read when the run sets its client, so changes apply from the next run, including values written by Set Client Variable earlier in the same run.
They need the Admin role. See Team and permissions.