How to Connect BoldDesk with Power Automate
You can connect BoldDesk with Power Automate by using BoldDesk webhooks, BoldDesk REST APIs, and Power Automate’s HTTP capabilities. While BoldDesk does not offer a native Microsoft Power Automate connector, you can still build custom workflows to sync data and automate actions between both platforms.
The following integration options are available:
| Integration Requirement | Recommended Option |
|---|---|
| Start a Power Automate flow when a BoldDesk ticket event occurs | Configure a BoldDesk webhook with the Power Automate When an HTTP request is received trigger. |
| Create or update BoldDesk records from Power Automate | Use the Power Automate HTTP action to call the BoldDesk REST API. |
| Reuse BoldDesk API operations across multiple flows | Create a Power Automate custom connector for the required BoldDesk API operations. |
These options allow BoldDesk ticket workflows to exchange information with applications such as Microsoft Teams, Outlook, SharePoint, Excel, and Dataverse.
Power Automate HTTP triggers, HTTP actions, and custom connectors may require a Power Automate Premium license.
Common Use Cases
- Send a Microsoft Teams notification when a ticket is created or updated.
- Create a BoldDesk ticket from Microsoft Forms, Outlook, SharePoint, or Dataverse.
- Update a BoldDesk ticket from an external business process.
- Send selected ticket information to Microsoft Excel or SharePoint.
- Start an approval or notification workflow from a BoldDesk ticket event.
- Build reusable BoldDesk operations through a Power Automate custom connector.
How the Integration Works
| Direction | BoldDesk Component | Power Automate Component |
|---|---|---|
| BoldDesk to Power Automate | Webhook | When an HTTP request is received trigger |
| Power Automate to BoldDesk | REST API | HTTP action |
| Reusable API operations | REST API | Power Automate custom connector |
Prerequisites
Before configuring the integration, ensure that you have:
| Requirement | Purpose |
|---|---|
| BoldDesk agent account with Manage API Keys permission | Required to generate an API key. |
| BoldDesk administrator access | Required to configure webhooks. |
| Power Automate Premium license | Required for HTTP triggers, HTTP actions, and custom connectors. |
| BoldDesk domain | Used in BoldDesk REST API URLs, such as yourcompany.bolddesk.com. |
Use a dedicated integration account to generate the BoldDesk API key. This helps prevent the integration from failing when an individual agent leaves the organization or changes roles.
Generate a BoldDesk API Key
Power Automate uses a BoldDesk API key to authenticate REST API requests.
-
Sign in to BoldDesk as an agent.
-
Click the profile avatar and select View profile & Settings.
-
Under Personal Settings, open the API Keys tab.
-
Click Create API Key.
-
Enter an Identification Name, such as
Power Automate integration. -
Click Create.
-
Copy the API key and store it securely.
- The API key cannot be viewed again after the dialog is closed.
- Do not store the key in an unsecured flow, email, document, chat message, or source-code repository. Use a secure service such as Azure Key Vault or a protected Power Platform environment variable.
If Access Denied appears when creating the API key, ask an administrator to add the Manage API Keys permission to the applicable role.
Start Power Automate from a BoldDesk Webhook
Use this integration direction when a BoldDesk ticket event should start a Power Automate flow.
For example, a webhook can start a flow when a ticket is:
-
Created.
-
Updated.
-
Assigned.
-
Replied to.
-
Moved to another status.
Create the Power Automate Flow
- Sign in to Power Automate.
- Select Create.
- Create an Instant cloud flow.
- Enter a flow name, such as
BoldDesk - Ticket Created. - Select When an HTTP request is received as the trigger.
- Click Create.
- Open the trigger.
- Set Who can trigger the flow? to Anyone.
- Add a temporary action, such as Compose.
- Save the flow.
- Open the trigger again and copy the generated HTTP URL.
Treat the generated HTTP URL as sensitive information. Anyone with access to the URL may be able to start the flow.
Configure the BoldDesk Webhook
-
In BoldDesk, go to Admin > Webhooks.
-
Click Add Webhook.
-
Configure the webhook details.
| Field | Configuration |
|---|---|
| Name | Enter a descriptive name, such as Ticket Created to Power Automate. |
| Description | Enter an optional description of the integration. |
| Module | Select Tickets. |
| Event | Select the ticket event that should start the flow, such as Created. |
| Destination URL | Paste the Power Automate HTTP URL. The URL must use HTTPS. |
| Request Type | Select POST. |
| Enable Authentication | Enable when the destination endpoint is configured to validate authentication. |
| Enable Signing | Enable when the receiving process must validate the integrity of the webhook payload. |
| Condition | Add optional conditions to restrict when the webhook runs. |
-
Under Payload, configure the content sent to Power Automate:
- Set Content Type to Json.
- Select Default or Advanced under Body Content.
- Select only the required ticket fields, such as Subject and Ticket URL.
- Enable Include all fields in the payload only when the flow requires the complete available payload.
-
Click Add.
Select only the fields required by the flow. Sending unnecessary ticket fields increases the payload size and may expose information that the downstream process does not require.
Test the Webhook Flow
-
Create or update a test ticket that matches the configured webhook event and conditions.
-
In Power Automate, open the flow.
-
Review the Run history.
-
Confirm that a successful run appears.
-
Open the successful run.
-
Review the HTTP trigger input.
-
Copy the trigger’s Body output.
-
Add a Parse JSON action.
-
Set Content to the trigger Body.
-
Click Use sample payload to generate schema.
-
Paste the copied body and generate the schema.
-
Replace the temporary action with the required workflow actions.
-
Save and test the flow again.
If the flow does not start, review Audit Logs > Webhook Failure Logs in BoldDesk.
Create a BoldDesk Ticket from Power Automate
Use this integration direction when an event in another application should create a ticket in BoldDesk.
Example triggers include:
- A Microsoft Forms response.
- A new SharePoint list item.
- A flagged Outlook email.
- A Dataverse record.
- A scheduled Power Automate flow.
- A message submitted through another Microsoft 365 application.
Configure the Power Automate Trigger
-
In Power Automate, select Create.
-
Select the required cloud-flow type.
-
In the flow designer, click Add a trigger.
-
Select the application and event that should start the flow.
Add the BoldDesk HTTP Request
- Below the trigger, add a new action.
- Search for and select the HTTP action.
- Set URI to:
https://yourcompany.bolddesk.com/api/v1/ticketsReplaceyourcompany.bolddesk.comwith your BoldDesk domain. - Set Method to POST.
- Add the following headers:
| Header | Value |
|---|---|
x-api-key |
Enter the BoldDesk API key generated earlier. |
Content-Type |
application/json |
- Add the ticket information in the request Body.
{
"brandId": 1,
"subject": "Refund request for order 1042",
"description": "Created from Power Automate",
"priorityId": 2,
"requesterEmailId": "[email protected]",
"isVisibleInCustomerPortal": true
}
Replace the sample values with valid BoldDesk values or dynamic content from the Power Automate trigger.
- Click Save.
- Test the flow using representative trigger data.
- Confirm that the HTTP action succeeds.
- Open BoldDesk and verify that the ticket was created.
- To reuse the returned ticket information later in the flow, add Parse JSON and use the HTTP action’s Body as the content.
Update a BoldDesk Ticket from Power Automate
Power Automate can also update an existing BoldDesk ticket.
- Identify the BoldDesk ticket ID.
- Add an HTTP action to the flow.
- Use the applicable BoldDesk ticket-update endpoint.
- Select the HTTP method specified in the BoldDesk API reference.
- Add the
x-api-keyandContent-Typeheaders. - Add the supported ticket changes in the request body.
- Save and test the flow.
- Verify the changes in the BoldDesk ticket history.
Use the current BoldDesk API reference to confirm the endpoint, HTTP method, required fields, and supported request body for each operation.
Build a Reusable Power Automate Custom Connector
Create a custom connector when multiple flows or teams need to reuse BoldDesk API operations without entering API URLs, headers, and request bodies each time.
- In Power Automate, go to Data > Custom connectors or More > Discover all > Custom connectors.
- Click New custom connector > Create from blank.
- Enter
BoldDeskas the connector name. - On the General tab, configure:
- Scheme: HTTPS
- Host:
yourcompany.bolddesk.com - Base URL:
/api/v1
- On the Security tab, select API Key.
- Configure:
- Parameter label:
API Key - Parameter name:
x-api-key - Parameter location: Header
- Parameter label:
- On the Definition tab, click New action.
- Enter an operation ID, such as
CreateTicket. - Under Request, click Import from sample.
- Select POST.
- Enter
/tickets. - Paste a representative JSON request body.
- Repeat the process for each required BoldDesk API operation.
- Click Create connector.
- Open the Test tab.
- Create a connection using the BoldDesk API key.
- Test every configured action.
- Share the connector or add it to a Power Platform solution when it must be moved between environments.
Power Automate custom connectors require a Premium license.
Troubleshooting
| Issue | Likely Cause | Resolution |
|---|---|---|
| Access Denied appears when creating an API key | The role does not include Manage API Keys, or API key creation is restricted for the account. | Ask an administrator to assign the required permission and use an eligible BoldDesk account. |
| HTTP action returns 401 Unauthorized | The API key is missing, incorrect, expired, or inactive. | Confirm that the x-api-key header name and API key are correct. |
| Ticket creation returns a validation error | A mandatory value is missing, or a supplied ID does not exist in BoldDesk. | Add the required fields and verify the brand, priority, requester, ticket form, and custom-field values. |
| Power Automate does not run after a ticket event | The webhook URL is incorrect, the condition does not match, or the request type is incorrect. | Copy the Power Automate URL again, use POST, and review Audit Logs > Webhook Failure Logs. |
| Power Automate rejects the webhook request | The HTTP trigger is not configured to allow the request. | Review Who can trigger the flow?, save the trigger, and copy the current HTTP URL. |
| HTTP capabilities are unavailable | The flow owner does not have a Power Automate Premium license. | Assign an eligible Premium license. |
| The flow creates duplicate BoldDesk tickets | The source event runs more than once or the flow has no duplicate-prevention logic. | Add an idempotency check using a stable source identifier before creating the ticket. |
| Required ticket data is missing in Power Automate | The fields were not included in the BoldDesk webhook payload. | Update the webhook payload and regenerate the Parse JSON schema. |
| Parse JSON fails after changing the webhook payload | The schema no longer matches the received webhook body. | Capture a new webhook sample and regenerate the schema. |
| The HTTP request succeeds but the ticket is not created as expected | The request used incorrect IDs or omitted mandatory fields. | Compare the request body with the current BoldDesk API request schema. |
Frequently Asked Questions
-
Does BoldDesk provide a native Power Automate connector?
No. Integrate BoldDesk and Power Automate by using BoldDesk webhooks, the BoldDesk REST API, and Power Automate HTTP capabilities. You can optionally create a reusable custom connector. -
When should I use a BoldDesk webhook?
Use a webhook when a BoldDesk event, such as ticket creation or update, should start a Power Automate flow. -
When should I use the BoldDesk REST API?
Use the REST API when an external event should create, retrieve, or update data in BoldDesk. -
Is a Power Automate Premium license required?
Yes. HTTP triggers, HTTP actions, and custom connectors are Premium capabilities. -
Can a webhook run only for selected tickets?
Yes. Add conditions to the BoldDesk webhook to restrict which ticket events are sent to Power Automate. -
Should I include every ticket field in the webhook payload?
Include only the fields required by the flow unless the use case specifically requires the complete available payload.