LC Premium Action
Last updated
Last updated
A custom webhook is a type of web service that allows you to send real-time updates or notifications from CRM to third-party service. With a custom webhook, you can define the format of the data you want to send.
You have the ability to send data requests to any URL of your choice without the need for coding or server operation.
You are free to choose any HTTP method that suits your needs, such as POST, GET, DELETE, or PUT.
We support various types of authorization methods, giving you the flexibility to choose the one that suits your needs when accessing the webhook.
In addition to sending a request body, our system also allows you to include headers and query parameters when sending requests to a webhook.
Headers can be used to provide additional information about the request, such as authentication credentials, content type, and cache control.
Query parameters, on the other hand, can be used to pass parameters to the webhook endpoint, allowing you to filter or modify the response data that you receive.
Custom Webhook premium feature allows you to map custom values in any structure that suits your requirements. We have a user-friendly textbox that provides autocomplete suggestions for all custom values, including inbound webhook variables.
This feature simplifies the mapping process and saves time by suggesting potential values that match your input. Additionally, it helps ensure accuracy and consistency in your data mapping.
A successful execution of the Custom Webhook Action depends on the successful response of the referenced API. Therefore, if errors are sent back, those will reflect on the Contact’s Workflow execution and cause the action to be Failed (and then skipped) or Retry with exponential backoffs.
In addition to what was stated above in #1, also make sure that the receiving server will be able to handle the amount of Executions that you are targeting for, or else you might end up with errors due to limits being reached of server issues. The Custom Webhook Action will get fired as soon as the Contact reaches the step, so make sure to add Contacts into the Workflow with the receiving server’s limits in mind.
