LeadConduit supports several custom delivery steps that can be used to configure an HTTP request to a recipient’s CRM or other system. In general, the request type corresponds to the “Content-Type”.
Here are the Content-Types supported by some of the custom integrations in LeadConduit.
- Custom reques t, supporting several HTTP Content-Types - can be configured as a GET or query request with urlencoded command-line parameters and as “Content-Type: application/xml”, among others
- JSON request - Content-Type: application/json
- Form POST reques t - Content-Type: application/x-www-form-urlencoded
How to add an HTTP Header to your HTTP request
When sending data to a receiving server, the posting instructions will sometimes require information in a HTTP Header. Here is how to specify the header in your custom delivery step.
- Edit the flow editor and click the delivery step in your flow
- Click “Edit Field Mappings”
- Click “+” to the right of the last mapping in order to add a new field mapping
- Pull down the recipient field dropdown to “Header”
- Enter the name of the header to the right of the “Header” label, and the value at the left.
Example 1. Here is the specification of an Authorization header (incidentally, this is an example of a Basic authorization containing the word “Basic,” followed by a space, followed by a base 64 encoded value):
Example 2. Here is the specification of an Accept header that instructs the recipient to reply with format application/json:
- Click “OK” and “Save”
Comments
0 comments
Please sign in to leave a comment.