Custom Actions are included on all plans at no additional cost. 15 Custom Objects and 100K records are available on all plans at no additional cost.

Yes, if you use the POST, PUT, or DELETE methods when testing a Custom Action it will perform those actions on your data. So, testing a DELETE call on a user will actually delete them.

Storing data is optional, but if you want to use external data returned from a Custom Action in Intercom (i.e. in a bot or Inbox workflow), it needs to be stored as custom data attributes on standard objects or Custom Objects in Intercom. Learn more about Custom Actions security and best practices here.

Note: Common scenarios where you might not need to store data are “action” request types PUT, POST, DELETE. For all GET requests, if you want to use the data in Intercom, you’ll need to store the data in Intercom.

This data is stored in Intercom.

You can only edit and update the description of a Custom Object and its attributes. If you need to change anything else, you’ll need to archive it and create a new one.

Yes, customers can take actions on data in a bot flow if you have set up the APIs that allow them to take that action.

Nested objects are not currently supported. This means that if, for example, the API is returning a list of orders as objects - we will first need to pull those orders in to identify the right order - and then, once we have the order ID, we can pull the items related to that order. With this, there would be a People-Order reference and a People-Item reference. Learn more about references here.

Tokens are stored as part of the header configuration in our database. These values are encrypted at rest. Find documentation on security at Intercom.

No, this is not supported explicitly with Custom Actions. Instead, the triggering is controlled by the workflow to ensure that teammates and customers get timely responses.

Reusing API error codes in subsequent bot flow is not currently supported. The bot flow has split paths by successful/unsuccessful Custom Action triggers. However, depending on the API, you could store API responses for subsequent bot workflows for branching. So if the API response JSON has an attribute that has response details like “status”, you could store that response status as a Conversation CDA and use it in bots for branching.

Custom Actions support both fixed and dynamic tokens for authentication. You can set up and manage your authentication tokens that you want to use in the request, which can then be added to the header.

Customers wanting to understand the impact of Custom Actions & Objects in Bots will need to use existing methods. For Custom Bots, this is most likely path-level analysis. For Resolution Bot, this is most likely answer level stats).