Myndbend Process Manager (MPM) provides a REST API for running common MPM operations from Zendesk Action Builder. You can use it to create or update child tickets, update a parent ticket, manage approvers, execute approval flows, schedule ticket work, run MPM workflows, and work with linked Jira issues.
This guide shows how to connect Zendesk securely to the MPM REST API, create a reusable custom action, and invoke it from an action flow.
Before you begin
You need:
- Myndbend Process Manager installed and configured in your Zendesk account.
- An MPM API EAP enabled for your account. If API EAP is not enabled, please contact Myndbend support at support@myndbend.com
- A Zendesk administrator account with access to Connections, Custom actions, and Action flows.
- IDs for any MPM templates, template sets, approval groups, approval flows, workflows, or Jira templates used by the action.
The current API specification is available in the MPM REST API documentation.
How authentication works
The API base URL is:
https://api.mpm.myndbend.comMPM authenticates requests with a Bearer token:
Authorization: Bearer YOUR_MPM_API_KEYDo not place the API key directly in a Zendesk custom action. Store it in a Zendesk connection so that the credential is not exposed in the action configuration. Zendesk connections support Bearer-token authentication and add the Authorization: Bearer header automatically. See Creating connections to integrate with external services.
Before moving to the next step, grab your MPM API key. Navigate to MPM Admin app > Webhook > Myndbend API:
Step 1: Create the MPM connection in Zendesk
- In Zendesk Admin Center, go to Apps and integrations > Connections > Connections.
- Click Add connection.
- Select Custom connection, then click Next.
- Enter a name such as myndbend_process_manager
- Select Bearer token as the authentication type.
- Paste the MPM API key into the token field. Paste only the token; do not add the word
Bearer. -
Set the allowed domain to:
api.mpm.myndbend.com
Save the connection.
The allowed domain is important: Zendesk sends the stored credential only to that hostname.
Step 2: Create a custom action
Create a separate Zendesk custom action for each MPM operation you want to use. Each endpoint has a different HTTP method, path, and request body, so one narrowly defined action is safer and easier to maintain than a generic action.
In Zendesk Admin Center, go to Apps and integrations > Actions > Custom actions, then click Create custom action:
You will need to create the Zendesk custom action using the MPM API documentation available here.
Example: Execute MPM create child tickets
Fill out the name and description:
- Name: MPM Create Onboarding tickets
- Description: Uses Myndbend Process Manager to create the onboarding tickets
Add these inputs:
| Input name | Type | Description |
|---|---|---|
ticket_id |
Number | ID of the Zendesk ticket on which MPM will execute the approval flow. |
Configure the API request:
| Setting | Value |
| Request method | POST |
| Endpoint URL | https://api.mpm.myndbend.com/api/tickets/{{ticket_id}}/child-tickets |
| Authentication | myndbend_process_manager |
| Query parameters | None |
| Additional headers | None |
The request body sent to MPM has this shape:
[{
"templates": [1,2,3]
}]You do not need to add Content-Type. Zendesk adds Content-Type: application/json automatically.
Custom action will should look like this:
Outputs
No outputs configured.
Step 3: Add the custom action to an action flow
- In Zendesk Admin Center, go to Apps and integrations > Actions > Action flows.
- Create a new action flow and give it a clear name and description.
- Add the trigger that should start the workflow. For example, use a ticket event, a schedule, or Run on demand, depending on the intended workflow and your Zendesk plan.
- Add a step below the trigger.
- Under Custom actions, select MPM Create Onboarding tickets .
- Map
ticket_idto the ticket ID supplied by the trigger. - Save and test the action flow.
- Activate the flow when it is ready.
Do not make the next step depend on MPM's background work already being complete. The custom action confirms submission, not completion. If completion must be verified, use a later ticket event or another explicit completion signal as the trigger for the next stage.
For general Action Builder instructions, see Creating action flows in Zendesk and Creating Zendesk custom actions.
MPM endpoint recipes
Using the same recipe as we showed in this article, you can create any custom action using the documentation from the MPM REST API page. For any questions, please reach out to support@myndbend.com.