Push data from your existing apps to Leadfwd using our no-code connector framework with Make (formerly Integromat).
Leadfwd leverages JSON powered webhooks to deliver and sync contacts from over 5,000 apps within the Make (formerly Integromat) ecosystem. No coding is required to leverage Leadfwd <> Make and the integrations can be setup seamlessly through your browser, just point and click.
Inbound Connectors (Push Contacts to Leadfwd and Sequences)
This article is going to specifically focus on Inbound Connectors, which process data sent via Make using their HTTP Request action and Leadfwd Webhooks.
Data imported to Leadfwd via Make (and your apps!) must be in the form of a new contact or to update an existing contact.
Prerequisites:
- Leadfwd Admin Access to manage Integrations and Connectors
- Integrations / Webhooks / Inbound Connectors
- Generate your Authorization Key + Secret
- Make (formerly Integromat) account (free plan is fine!)
- Third-party app credentials (in our example we are connecting Hubspot to Leadfwd)
- Most Make apps use the Oauth token framework that requires a login to connect your app, like Hubspot, to Make. Other apps may require API keys or tokens. Consult the Make app guide to figure out which you will need. Expect to need credentials as an Admin or Owner from your third-party app to successfully connect to Make.
In this Article
- Create a new Scenario in Make
- Create an Inbound Connector in Leadfwd
- Configure your Scenario in Make
- Setup custom data field properties to sync (Make -> Leadfwd)
- Basic Authentication (Auth Key + Auth Secret)
- Test your Scenario
- Activate your Scenario
Send New Contacts from HubSpot CRM to Leadfwd
Create a new Scenario in Make
- Select your source app. (In our example we are using HubSpot CRM)
- Choose the condition. (In our example we want new Contacts created in HubSpot to sync to Leadfwd)
- Choose the action (search for HTTP) and select the Make a request option
Create an Inbound Connector in Leadfwd
- Navigate to Settings > Integrations > Webhooks and select Inbound Connectors and then click Create Connector
- Choose a Name that will easily translate to the connectors Purpose and Select your database (i.e. Contacts)
- Click Save Connector
- Click Inbound Connectors and Copy the Connector Endpoint URL
Configure the HTTP Request action
Apply the Webhook URL Endpoint
Select Method: POST
Select Body type: Raw
Select Content type: JSON (application/json)
Setup Contact data fields to sync to Leadfwd
JSON String Format |
{"leadfwd_sequence":"","leadfwd_tags":"","name":"","email":""} |
While it may sound highly-technical, JSON is just a structure for sending data from one platform to another.
- "name" and "email" are custom data field properties in Leadfwd Contacts
- "leadfwd_sequence_id" allows you define a Sequence ID to enroll a contact into that is pushed to Leadfwd with Make.
- "leadfwd_tags" allows you to define a one or many tags, separated by commas to apply to the contact that is pushed to Leadfwd with Make.
Additional custom data field properties can be included simply by adding another entry, shown below with the addition of the Company data field property:
{"leadfwd_sequence":"","leadfwd_tags":"","name":"","email":"","company":""}
You'll drag and drop the corresponding HubSpot source data object (i.e. First Name, Company, Email) into the JSON string and between the "" for each Leadfwd data field property that you're mapping data. Watch below:
The properties from HubSpot that have been added to our Request content will automatically be filled with the proper data before they're submitted to Leadfwd, for each unique Contact.
Basic Auth
All inbound requests are authenticated using a Auth Key and Secret that are generated in your Leadfwd account. Within Make the User name field will represent your Auth Key and the Password will be your Auth Secret.
If you haven't already done so, you can generate your Auth Key and Secret by navigating to Settings > Integrations > Webhooks
Testing your Scenario
Once your Scenario is completed you can validate that everything is working properly using the 'Run once' option.
In our example use case with HubSpot we are specifically monitoring for new contacts created, so we had to create a test record in HubSpot before executing the Run once option.
Once you click Run once you can check your Contacts view to see if your new record was synchronized. You can also check the Platform Log to see if the POST was successful from your Make Scenario and if it wasn't, see what the issue was.
If there is no entry in Platform Logs for your 'Run once' test, then there was either no attempt to POST to Leadfwd by Make or your URL endpoint is incorrect. In which case you'll want to consult the logging for your scenario directly. You'll want to see that the Orange Condition operation was completed and the Blue Action operation was completed. If you're having issues, please reach out to our team to assist.
Activate the Scenario
Once you validate that the scenario is working as expected, you can activate the workflow by turning it on.
Comments
0 comments
Please sign in to leave a comment.