Integrate HTTP Request (GET/POST) with LeadsBridge

Intro

The HTTP Request is a request-response protocol between a client and server that allows the exchange of information between systems. It is a customizable integration and it's typically used to send data to custom platforms.

In this article, you'll learn how to connect your LeadsBridge account with HTTP Request (GET/POST).

Connect HTTP Request (GET/POST) integration

Before you start

Authorize HTTP Request (GET/POST) integration

Setup your HTTP Request (GET/POST) integration

1. Click on Connect HTTP Request (GET/POST)
2. Click on Create new integration to connect your HTTP Request (GET/POST) (or select an existing one from the dropdown if you already connected it)
3. A popup wil be opened where you can authorize the HTTP Request (GET/POST) integration
4. Fill URL field to connect HTTP Request (GET/POST) with LeadsBridge
5. Click on the Authorize button
6. You can choose a name for this HTTP Request (GET/POST) and LeadsBridge integration (you can also edit it later)
7. Once done, click on Continue button and you will get back to the bridge experience where you could choose additional integration settings
8. Now that your HTTP Request (GET/POST) is connected, you can continue with the set-up of your bridge

Configuration details for HTTP Request (GET/POST)

How to get URL

• URL - mandatory: where the system you'd like to send information to is located.


• Method - mandatory: the request method your system may receive as the indication of the desired action to be performed.
  • POST is the default value. It's used to send data to a server to create/update a resource and it's one of the most common HTTP methods. If you're unsure about what you should select, leave it as is.


• Content Type - mandatory: is used to indicate the media type of the resource. Works as the content type description for the message body.
  • application/x-www-form-urlencoded is the most common encoding type. Use this as long as you're not using any JSON or XML language on the request body.

• Success pattern - optional: the message your system replies with once the request was received successfully.


• Failure pattern - optional: an error message your system sends when there's an issue with the request.
• Skip encoding parameters in URL - optional: if enabled prevent the encoding of special characters in the URL parameters

Other Info

• Body - mandatory: the message Body is where all the data is set to eventually form the HTTP Request that will be sent to insert each lead into your system.
  • Body syntax should be write as follows:[code]"field_id": "value″[/code]"field_id" is the unique identifier of the field inside your CRM/platform; "value" can be static (number or text that will be the same for every lead synced) or dynamic.
  
  
  • To create dynamic values just enter the field name between the double @@ symbols, that will results in a @@field_name@@ syntax. The field name can be whatever you'd like, it will help you recognize the field inside the bridge settings later.
    Dynamic fields will be displayed on the Fields Matching step of the bridge, where you will be able to match them with lead's information.
  
  
  • That said, if we have a full_name field on our platform to store the lead's full name, we should use the following syntax:
    [code]full_name: @@FullName@@[/code]Please check HTTP common questions for code examples.

Which entity concepts we support for HTTP Request (GET/POST)

With LeadsBridge you may use these entity concepts for HTTP Request (GET/POST).

1. Lead

   Leads are people who are interested in your product or service.

Common questions for HTTP Request (GET/POST)

HTTP Request code example

JSON code example

Are Success and Failure patterns mandatory?

I received a timeout error, what should I do?

Could you please help to set up the integration?

Do you need help?

Here some additional resources:

• LeadsBridge KNOWLEDGE BASE
• Contact support from your account clicking on the top right Support button