Intercom is a set of communication tools within a single platform that allows direct communication between businesses and their clients. Intercom has excellent developer documentation, which is what this connection and document is based off.
In this article:
Before implementing this connector in UDH it is strongly advised that you read and test the sections that are applicable to your business.
When you create your token, it is likey you will need to extend its scope to leverage the request types for your business' needs. You can request this extension by asking the Intercom team.
To create your token:
Skip this section if you are familiar with setting up streams.
I consider it best practice to always set up streams for your individual use cases or needs, unless you are sending all data to a vendor. This will allow you more granular control over the connections, as well as the ability to alter them in the future without affecting other requests. Having multiple streams and actions will increase maintenance, but may save complications down the line.
To do this:
For this example, I am going to create a Webhook that will pass a new user event. Intercom's API documentation on this type of request can be found here.
To build a custom webhook:
With everything configured you can now test the setup with Trace.
If successful, you will see a successful Action Processed in Trace and the data within Intercom.
If unsuccessful follow the errors on the Intercom Webhook connector in the My Connectors section under Act tab. I would also recommend testing with Postman at this stage with your exact webhook configuration. Ensure you replace the mappings with actual values.