How to integrate Centercode with Zapier

Accomplish an infinite number of integrations by connecting Centercode to Zapier

This article applies to ProTeam, and Legacy editions.

Note that while Centercode’s integration features are intended to be approachable by a Centercode Program Manager, you might need to enlist help from an internal technical resource and refer to our vocabulary and troubleshooting documentation.

Zapier is an incredibly powerful tool that has the ability to bridge multiple systems into a single workflow. It offers hundreds of tools and functions, including first-class endpoints and open-ended methods like capturing webhooks, processing data it receives, sending its own webhooks to various custom endpoints, and much, much more. Below are some potential (common) integration use cases for Zapier. 

Consider using Zapier to

Removing Centercode users via Zapier

With Centercode's external listeners, users can leverage Zapier to delete or remove user accounts from the platform. This makes it easy for users to remove Centercode accounts through Zapier requests, without needing to manually access the platform. These API integrations are particularly useful for adhering to user account deletion requests, as well as strict privacy or GDPR compliance, within your Centercode implementation.

Preparing the Macro Listener in Centercode

To trigger the “remove users" action in Centercode through a Zapier automation, you'll need to configure an external listener and a community-level macro. 

You’ll start by:

  1. Creating the macro that defines the action you want to take, such as removing a user or sending an email
  2. Set up an external Listener that can receive the automation request from Zapier and trigger the macro in Centercode
  3. Once the macro and external listener are set up, you can copy the endpoint URL provided by Centercode and use it in your Zapier automation

For more detailed instructions on how to set up this integration within Centercode, check out the relevant knowledge base article on How to delete/remove user accounts through API integrations.

Preparing your POST in Zapier

After configuring the Centercode side of the integration, you'll receive an endpoint URL to use in your Zapier integration.

Within Zapier’s help center article Set up an API request action, Zapier provides instructions for setting up an API request action that enables users to trigger custom requests, such as deleting users in Centercode. The article walks you through the steps to create the API request action, including configuring the action settings, selecting the target API endpoint in Centercode, and specifying the user account to be deleted.

Creating Feedback in Centercode from Zapier

With this integration, you can automate the process of creating feedback items in Centercode. This integration not only streamlines your workflow but also ensures that all customer feedback is captured and organized in a centralized location for better product analysis and decision-making.

Preparing the External Source within Centercode

To enable your Centercode implementation to receive feedback from external systems like Zapier, you can use the External Sources Integration Guide to create actionable feedback tickets that function just like regular feedback, complete with workflow, Impact Scoring, and other automation features. 

As outlined within the external sources guide, you’ll:

  • Create a new external source within the desired project and feedback type 
  • Choose the appropriate workflow starting point
  • Configure the external source to collect incoming fields and map them to your feedback form
  • Once configured, copy the endpoint URL for use in your Zapier automation

To route feedback to the correct feedback type, you’ll configure an external source for each feedback type and set up a unique API endpoint. Zapier can then transmit feedback to the appropriate endpoint associated with the intended feedback type within Centercode.

Preparing the POST within Zapier

By following these steps from Zapier Trigger Zaps from webhooks, you’ll set up a webhook as the trigger for a Zap, including how to configure the webhook endpoint, map the data fields, and test the webhook.


API integrations typically produce two types of results: success or failure. When working with API testing tools, Centercode implementation, or third-party applications, you may encounter various responses that fall into one of these two categories. Here are some examples of the types of responses you may encounter.

400 Bad Request

  • This error can occur due to a variety of reasons, such as incorrect syntax, missing or invalid parameters, or incorrect request formatting
  • When you encounter a 400 error code, you should review the request parameters and formatting to ensure they are correct and properly structured
  • Once you have identified and corrected the issue, you can resubmit the request to the server and expect a successful response

401 Unauthorized

  • Verify that the API key or authentication credentials used in the external source configuration within Centercode are correct and up-to-date
  • Check that the API key or credentials have sufficient permissions to perform the desired actions
  • Confirm that the receiving system is expecting an authenticated request and that the credentials being used match the expected format

403 Forbidden

  • Indicates that your API request does not have sufficient permissions to complete the desired action
  • To resolve a 403 error, review and adjust the permissions and access settings for the user account or API key

404 Not Found

  • Verify that the specified resource (such as the API endpoint or feedback type) exists in the specified project within Centercode
  • Check that the URL or API endpoint being used in the external source configuration is correctly formatted and does not contain any typos
  • Ensure that the receiving system is sending data to the correct URL or API endpoint

422 Unprocessable Entity

  • Verify that the data being sent from the external system matches the expected field names and data types within Centercode
  • Check that the external source is configured to properly collect incoming fields and map them to the appropriate feedback form
  • For Zapier, check that the outgoing data is in the correct format for the REST API

500 Internal Server Error

  • Check that the server is running within Zapier and that there are no issues with its configuration
  • Review any server logs or error messages within Zapier for additional information on the cause of the error
  • If necessary, contact Zapier support for assistance with troubleshooting the issue

503 Service Unavailable

  • Verify that the server is not undergoing maintenance or experiencing high traffic
  • If the issue persists, try again later
  • If necessary, contact Zapier support for assistance with troubleshooting the issue

For additional troubleshooting reference, please refer to our knowledge base article Understanding Integration Terms and Troubleshooting Status Codes. Additionally, you can consult with a Zapier integration specialist or Centercode Support team member to get additional assistance with troubleshooting your issue.