MSP Process

Triggr uses MSP Process to verify end users by code, Duo Push or Microsoft Authenticator, share secrets through secure links, and send contact update forms. You need an MSP Process Pro or Pro+AI plan, an admin-level user, and a PSA integration in MSP Process for verification.

Set up MSP Process

Copy a public API key

In MSP Process (app.mspprocess.com), go to Settings > Account Settings > API Keys, click Public API key and copy the key. See Using the MSP Process APIs.

Turn on the End-User Verification API

Go to Identity Management > Verification > Verification Settings, expand API Settings, tick Enable, select your main PSA integration and click Submit. MSP Process looks up end users in that PSA.

Set up push verification (optional)

Verify Using Duo Push needs MSP Process’s Duo integration, with Duo Admin API and Auth API applications under Settings > Integrations > Security Integrations. Verify Using Microsoft Authenticator needs its Authenticator app deployed to the end user’s tenant.

Connect it in Triggr

Open the integration

Go to Integrations > MSP Process and click Configure on the Base Configuration card.

The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.

Enter the key

Paste the key into API Key and click Save Configuration. One key covers every client; to test it, run a Test Connection step.

The MSP Process configuration window with an API Key field, an Allow insecure TLS switch under Advanced, and a Save Configuration button.

Use MSP Process in workflows

Every action except Test Connection takes JSON in jsonBody. Email addresses and phone numbers must belong to a contact in the PSA selected in API Settings.

Action	`jsonBody`
Send Verification Code by Email	`{"email": "jane.smith@contoso.com"}`
Send Verification Code by SMS	`{"phone": "+15551234567"}`
Check Verification Code	`{"verificationCode": "123456"}`
Verify Using Duo Push, Verify Using Microsoft Authenticator	`{"email": "jane.smith@contoso.com"}`
Create Secure Text Link	`value` (required), `removeAfterView` (`true` removes it once viewed), `expirationDateUtc` (UTC)
Send Secure Link	`type` (`Phone` or `Email`), `value` (recipient), `link`, `content` and, for email, `subject`. Only `subject` is optional.
Send Contact Update Form	`crmId`, `contactId`, and `contactEmail` or `contactPhone` (at least one)

For example, to send a link from Create Secure Text Link by email:

{
  "type": "Email",
  "value": "jane.smith@contoso.com",
  "link": "the secure link",
  "content": "Here is your new password.",
  "subject": "Your new account"
}

Troubleshooting

Every action fails with 401 Unauthorized

Copy the key again from the Public API Key window and paste it in full with Edit on the Base Configuration card.

Test Connection works but verification fails

Turn on the End-User Verification API and select a PSA, as in Set up MSP Process. Push verification also needs MSP Process’s Duo or Authenticator integration.

The end user isn't found

Check an active contact with that email address or mobile number exists in the PSA selected in API Settings.

400 Bad Request

The response’s message says what’s wrong, such as a missing field or invalid address. Check jsonBody against the table above.

⌘I

Integrations

Desktop agent

Network access

Microsoft

PSA

RMM and endpoint management

Documentation and assets

Identity and passwords

Verification and secret sharing

Security

Security awareness training

Backup

Networking

Monitoring

Licensing and distribution

Communication

CRM and marketing

HR

Productivity

Accounting

Other tools

Set up MSP Process

Connect it in Triggr

Use MSP Process in workflows

Troubleshooting

​Set up MSP Process

​Connect it in Triggr

​Use MSP Process in workflows

​Troubleshooting

Set up MSP Process

Connect it in Triggr

Use MSP Process in workflows

Troubleshooting