Zapier Integration with BoldDesk

3 mins read

Updated:

Zapier is a web-based automation tool that allows you to integrate with various apps and services in less time. This enables you to use Zaps for creating workflow sequences.

A Zap is a pre-programmed workflow that includes a trigger and one or more actions. These actions will execute whenever the trigger event occurs.

Check out this video for more information:

Supported Triggers

The supported triggers are listed in the following table.

Trigger Events	Triggered When
Create Ticket	A new ticket is created.
Update Ticket	Any fields are changed in the existing ticket. A ticket is marked as spam. A ticket is removed from spam. A ticket is deleted softly. A ticket is restored.
Create Ticket Reply	A new reply is created.
Create Ticket Note	A new note is added.
Create Contact	A new contact is created.
Update Contact	Any fields are changed in the existing contact. A contact is blocked. A contact is unblocked. A contact is deleted softly. A contact is restored.
Create Contact Group	A new contact group is created.
Update Contact Group	Any fields are changed in the existing contact group.

Supported Actions

The supported actions are listed in the following table.

Actions	Description
Create Ticket	Create a new ticket.
Update Ticket	Update an existing ticket.
Create Ticket Reply	Create a reply to the existing ticket.
Create Ticket Note	Create a note to the existing ticket.
Create Contact	Create a new contact.
Update Contact	Update an existing contact.
Create Contact Group	Create a new contact group.
Update Contact Group	Update an existing contact group.
Find Ticket	Search for a ticket by ticket ID.
Find Contact	Search for a contact (both agent and customer) by email ID.
Find Contact Group	Search for a contact group by name.

Make a Zap Trigger for BoldDesk

Follow the steps below to create a trigger in Zap:

Sign in to your Zapier account or create a new account if you don’t have one already.
In the left sidebar, navigate to the Zaps menu and click Create Zap.
To configure the BoldDesk trigger, click Trigger.
Search and select the app to perform the action. Then, select the trigger event from the dropdown list and click Continue.
If you have already connected a BoldDesk account, select it from the dropdown list or connect a new account.
To connect a new BoldDesk account, enter the Domain Name and API Key and click Continue when the account is connected.
Select the required brand to create a trigger and click Continue.

Selecting the brand will activate only the Zap if the ticket belongs to the selected brand. To trigger all brands, leave the brand field empty.

Click Test Trigger to get the most recent data and click Continue.

To get more recent data from the BoldDesk app, click Load More.

Make a Zap Action for BoldDesk

Follow the steps below to create an action in Zap:

Sign in to your Zapier account or create a new account if you don’t have one already.
In the left sidebar, navigate to the Zaps menu and click Create Zap.
To configure the BoldDesk action, click Action.
Search and select the app to perform the action. Then, select the action event from the dropdown list and click Continue.
If you have already connected a BoldDesk account, select it from the dropdown list or connect a new account.
To connect a new BoldDesk account, enter the Domain Name and API Key and click Continue.
Fill in the required fields from the previous steps or choose values from the dropdown list and click Continue.

The fields will be refreshed/rendered based on the selected brand.

Click Test and Continue to post the data to the API to create or update the details in BoldDesk.

If there are any errors, they will be displayed.

Click Turn on Zap to enable the Zap after completing the test.

Troubleshoot “Invoke Payload Too Large” Error

When you click Test Trigger in the Zap editor, you may experience the error below.

Error while hydrating data from BoldDesk: Invoke payload too large (14908065 bytes but max is 6291456 bytes)

To resolve the error, please observe the following:

Zapier imposes a size limitation when testing triggers. Specifically, the response payload must not exceed 6MB when using the Test Trigger function in the Zap editor.
During trigger testing, BoldDesk automatically loads the three most recent records as sample data. To remain within the size limit, consider decreasing the payload size—for instance, by shortening description fields or removing unnecessary content—before testing again.
This size limitation is applicable only within the editor during setup. Once the Zap is live, it can process larger datasets without any problems.
Zapier may throw a “payload too large” error even if a test is not manually triggered. This usually happens when Zapier automatically attempts to fetch sample data during setup or refresh. To resolve this, create 3 new tickets in BoldDesk with short descriptions and then try setting up the trigger again.

Ticket Form ID Not Showing in Zapier Integration – How to Resolve

Was this article useful?

Dislike

Comments (0)