Custom Touch Point Behaviors Channel

Paul Whelan
Paul Whelan
  • Updated

Why Use This Channel

This webhook channel allows you to import behavior data from another platform into Act-On. When the Webhook Source is triggered, a new custom behavior will be added to Custom Touch Point Behaviors. Behaviors can be used in Segmentation and Lead Scoring. 

How To Set Up an Incoming Webhook in Act-On for Custom Touch Point Behaviors

Create a New Webhook

  1. Go to Settings > Connectors > Custom Integrations > Incoming Webhooks.

  2. Click + Create Webhook.

  3. Select Custom from Webhook source.

  4. Enable Verification.

  5. Enter a Verification method. Authentication is added and needs to be included with the outgoing webhook. This is to validate the authenticity of the incoming webhook:

    Screenshot 2023-09-27 at 7.02.24 PM.png 
    • If you select Token, Act-On will create one for you. 
    • If you select Basic, enter a username and password. It can be anything as long as it is secure.
    • If you select Digital Signature, enter all the parameters found in the developer documentation for the Webhook Sender.

  6. Continue to mappings if the payload of the outgoing webhook is already known, otherwise, skip to Create.
    •  Example: a Calendly payload will look like this:



        • Follow these instructions for more details on how to manage webhooks in Calendly.

  7. Enable Content Mappings.

  8. Select Custom Touch Point Behaviors from the Channel drop-down.

  9. Choose the appropriate behavior type.
    • The list displays configured behavior types in Contacts > Other > Custom Touch Points. For more details on how to manage Custom Touch Point Behaviors refer to this article.

  10. Map the variables from the outgoing webhook to the corresponding Act-On field
    • Select a behavior type that is appropriate based on the data being exchanged from the Source Webhook: eg. "Calendly Signups". This is configured in Contacts > Other Lists > Custom Touch Points.
    • Map a variable from the payload to the Action field. We recommend you choose a field that is appropriate based on the data being exchanged from the Source Webhook, such as the name of the meeting. This is variable payload.scheduled_event.name

      Screenshot 2023-09-27 at 7.21.00 PM.png

  11. Click Create to save your webhook.

Test Your Webhook

Incoming webhooks must be tested before being enabled to be operational and actively process messages from third parties. Testing verifies the payload structure and validates the required data is present; however, it does not take any action in Act-On based on the received data. No test data will be saved in Act-On contacts from the test.



Example of a successful test:



Example of a failed test



Note: Testing can be skipped on Create but it is required to be complete and successful prior to enabling the webhook:

 

Edit Your Webhook

All webhooks can be edited; however, only certain fields are editable. Furthermore, retesting is required if critical fields that impact the webhook function are changed.

Field Visible Editable Retest Required
Webhook name Yes Y N
Description Yes Y N
Webhook source Yes N N/A
Authentication PW is not visible
Token is not visible
Y Y
PW can only be re-entered
Token can only be re-generated
Channel Yes N N/A
Data mappings Yes (only for Custom) Y Y

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request