Syncing 10,000 leads/mo? Get a demo
LeadsBridge
Sign up for free
FTP/SFTP logo
+
HTTP Request (GET/POST) logo

How to connect FTP/SFTP with HTTP Request (GET/POST)

SIGN UP FOR FREE

Connect FTP/SFTP to HTTP Request (GET/POST) with LeadsBridge

FTP/SFTP » HTTP Request (GET/POST)

In this article, you'll learn how to set up the bridge and connect FTP/SFTP to My CRM Example using LeadsBridge.

How to set up your bridge step-by-step tutorial

Before you start

  1. Head over to the left sidebar and click on the Create new Bridge green button
  2. You'll be taken to the first step of the bridge creation

Step 1: Choose the apps you want to connect

  1. Choose FTP/SFTP as the source for your bridge
  2. Choose HTTP Request (GET/POST) as the destination for your bridge
  3. Click on the Continue button
  4. At this point you can choose a name for your bridge (this will only be visible inside LeadsBridge and you can also edit it later)

Step 2: Configure your FTP/SFTP with HTTP Request (GET/POST)

Step 2.A: Setup your FTP/SFTP integration

  1. Click on Connect FTP/SFTP
  2. Click on Create new integration to connect your FTP/SFTP (or select an existing one from the dropdown if you already connected it)
  3. A popup wil be opened where you can authorize the FTP/SFTP integration
  4. Fill Use SFTP? (Secure FTP), FTP Host, FTP Port, FTP Username, FTP Password, Root directory, Destination filename pattern, Private Key, Charset, File's extension (eg. txt), Fields Separator Char, Headers row number (default 0) field to connect FTP/SFTP with LeadsBridge
  5. Click on the Authorize button
  6. You can choose a name for this FTP/SFTP 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 FTP/SFTP is connected, you can continue with the set-up of your bridge

Step 2.B: Configuration details for FTP/SFTP

How to get Use SFTP? (Secure FTP), FTP Host, FTP Port, FTP Username, FTP Password, Root directory, Destination filename pattern, Private Key, Charset, File's extension (eg. txt), Fields Separator Char, Headers row number (default 0)

Some FTP/SFTP details such as host name, username and password are required for accessing your files on the server by using an FTP client. The FTP details will comprise a server address (similar to ftp.yourdomain.com), a username and a password.

In case that you don't have, or you don't know, those details, you should contact your web hosting provider, and they will be able to give you this information.

Usually, web hosting services provide you these details after you sign up for a web hosting package. In most cases you’ll receive your FTP/SFTP information details in the welcome email sent from your web host provider after signing up to their services.

Below you can find a short description for each field from the FTP/SFTP integration:

  • Use SFTP This toggle will allow you to use the Secure mode (SFTP), if your FTP server implements it

  • FTP Host This is the hosting server name

  • FTP Port This is the server port, the default port for FTP is 21, and for SFTP is 22

  • FTP Username/Password Your FTP credentials, usually they're the same as your cPanel login details

  • Root Directory This is the folder in your FTP service where you would read files from or put files to. If any provided, the root dir will be used

  • Headers row number This is the row index (0 based) in which the file headers are located

  • Charset This is the charset encoding of your input files

  • File's extension This is the extensions that will be used to filter files in case you use your integration as a Source

  • Fields Separator Char The char used as separator in the CSV file

  • Destination filename pattern This value will be used to define the name of the output file in case the integration is used as Destination. You may use Date and Time patterns chars such as Y/m/d H:i:s. Notice that you should type the pattern inside square brackets, for instance [Ymd]

How to get File's extension (eg. txt)

Please note that when used as Source FTP/SFTP, it only accepts .csv and .xls files. When used as Destination the integration only accepts .csv

Step 2.C: 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

Step 2.D: 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.

Step 2.E: Email Receipt (Optional)

You may choose to receive an email receipt for each incoming lead.

  • Type the address(es) where you'd like to receive the receipt
  • You may also modify the Subject line of the email

Step 3: Fields Mapping

Here you'll be able to map your FTP/SFTP information with your HTTP Request (GET/POST) fields.

  1. You will have HTTP Request (GET/POST) fields on the left. Match the information you wish to pass align from FTP/SFTP
  2. Based on HTTP Request (GET/POST) functionality, some fields might be required; if this is the case, you can identify those fields with a * (star), so be sure to map all them
  3. You can also use the functions to customize information like reformatting dates and times or modifying text, phone numbers and so on.
  4. You may leave blank the box of a field's information you don't want to send through. Clicking on the Show unmapped fields button you will have visibility on all the available fields still not mapped

Step 3.A: Leads Filter (Optional)

If you'd like you could add a filter for incoming leads. This filter will sync only leads that meet the configured conditions

  1. Click on the link Add Filter for Incoming Leads on the top left
  2. A popup wil be opened where you can configure the filter
  3. You can define a series of condition to filter the leads. The lead will be synced only when all the conditions will be met
  4. Once finished, click the Save Changes button to switch back to the Fields Mapping to continue with the bridge configuration

Step 3.B Test Connection (Optional)

Once you’ve mapped all the fields that you need, if available, you can run a test of your connection by clicking on the Test Connection button.

Step 4: Save and Publish

  • Click on the Save and publish button

Congratulations! Now your bridge is up and running

Do you need help?

Here some additional resources: