Outgoing WebHooks





One of the unique features of TexAu over the competition is the ability to send ingoing and outgoing webhooks at every node of your workflows. Moreover, it's not task-based and instant so this won't count much in your daily execution time.

This feature could serve multiple purposes such as:

• sending profiles to your CRM with enriched data from TexAu
• sending data to Zapier, Integromat, Pabbly, Integrately for interconnecting to other services. A common use case is to send emails or updating rows from a google sheet with additional data.
• sending custom notifications and alerts.
• retrieve leads from Albacross or Happierleads

Today, we will cover the first use case and send enriched contact data to your CRM.

Virtually any CRMs which have a Zapier, Make (formerly Integromat), or Pabbly application can be used in this example.

Here we will demonstrate how to do so using Integromat and Salesflare CRM, the process will be exactly the same for all CRMs.

Integromat is a very affordable and reliable alternative to Zapier with tons of apps you can use.

Their free monthly plan gives 1000 free tasks per month:



Integromat

Start With Sales Navigator Leads Search Filter

Let's start with Sales Navigator lead search filter to narrow down a juicy list of prospects.

Here, we will focus on leads with those criteria:

• profiles who posted on LinkedIn in the past 30 days
• profiles from a particular country location
• Wipeout 1st-degree connections (only 2nd and 3rd-degree connections)
• Remove our existing clients' accounts from the Company filter
• Last, we will add the option to "Remove Viewed Leads From Search" which allows seeing leads above the 2500 profiles per search limitation. That means that every time we will scrape profiles from this list, those will be removed from the filter. So each time we will schedule or run our workflow manually only new profiles will appear.



For filtering your existing clients, negative filters always come in handy:



Just click on the little 🚫 sign when you hover on the blue bullet filter like this, it will turn in red as a negative filter and all its related results from the search will be removed from the list:



Once you are done with your lead search filter, save it:



Then go to the Saved Searches tab and click "Saved Lead Searches". There you'll find the list of all your saved lead searches:



Now, copy the URL of our Lead Search in a safe place on your notepad, we will use it later:



Building The Workflow in TexAu



1. Scrape Sales Navigator Lead Search Results.
2. Convert all the Sales Navigator profile URLs to regular LinkedIn profile URLs.
3. Scrape all the details of each profile by visiting their page.
4. Find their company email from First Name, Last Name, and Company Domain.
5. Verify those emails.
6. Send outgoing webhook data to Integromat to add each profile's details in our CRM.

Here, we won't cover all the workflow settings since this has been explained in other tutorials.

Instead, we will explain how to use webhooks to send data to your CRM or other applications.

To send data to an external software you will need to send an outgoing webhook also called an HTTP POST request.

For this, click the blue (+) button to add a new module to your workflow, this time select "Send a Webhook POST request":



To use outgoing webhooks in TexAu, we will need a webhook URL to input:



For this, create a new scenario in Integromat. A scenario is the equivalent of a workflow in Integromat:



There, click on the big (+) blue button to add your first trigger module: Webhooks.



Now, click on the Webhooks module and click the "Add" button to generate a webhook URL:



Give it a memorable name like "TexAu trigger" and save it.

Now Integromat will display a red spinning button waiting for the webhook response. Leave it spinning that way, we will send a test request from TexAu in few minutes.



After creating your webhook URL in Integromat, paste it in the "PATH" field in TexAu:



Now back in the TexAu webhook module, add all the fields you need to send leads data to your CRM such as:

• First Name
• Last Name
• Company Name
• Job Title
• Linkedin Profile
• ... or whatever fields or custom fields you have in your CRM

To add a new field, click on the "+ADD POST DATA" blue button.

Then add:

• Key Name: the name of the field data you want to create.
• Description: this one is optional and can be left empty.



In this example, I created the fields below to send the following LinkedIn profile data to Salesflare:

• Company Name
• Website
• Email
• First Name
• Last Name
• Mobile Phone
• Profile Image
• LinkedIn Profile



Once those fields are created, we will need to map each of them with the corresponding TexAu variables. Those variables are the data we scraped from LinkedIn with our workflow, most of those coming from the automation module "Scrape a LinkedIn Profile". The email variable is taken from the "Email Verifier" module:



Once all the variables are mapped it should look like this:







Now it's time to test your webhook response. In order to do so, we will use the "Test Webhook" feature in TexAu. You'll find this under the webhook module settings on the left tab.

Input any data you want here, it's only for sending a test request that we will map later on in Integromat.

Once you are done filling test data, push the "TEST WEBHOOK" button at the bottom to send your test request:



If all goes well, you should be able to see the confirmation after a few seconds in Integromat:



Set Up Integromat Scenario to Create Contacts & Accounts

Now, let's go back to Salesflare and create an API Key to connect the Salesflare app in Integromat:



Back in Integromat, add a new module after the webhook trigger we created before and use the Salesflare app called "Create an Account".

Here we will create a new company account in Salesflare from the company data we extracted before with TexAu:



Click and open the Salesflare module and in the "Connection" field then click "Add" to enter the API Key you just created before:



Now, paste your API Key, then click "Continue":



Now, let's map the TexAu variables we obtained from the webhook trigger module after sending a successful test request.



Add Company Name and Website variables to their corresponding fields:



Now in Integromat add a new Salesflare app: "Create a Contact".

Like we did before, add your Salesflare API Key to connect this new app.



Same as before, we will map all the variables from TexAu but also the Account and Contact ID's we mapped from the last step, namely:

• First Name
• Last Name
• Email
• Profile Image
• Mobile Phone





For the mobile phone field, don't forget to add its type:





Very last step: add the "Add a Contact to an Account" Salesflare app and add your API Key again:



In the "Create an Account" Salesflare app, enable the "map" toggle above each field and add "Account ID" and "Contact ID" then click OK.





Once you are all set and done, save your Integromat Scenario:



You'll be able to retrieve this scenario from the "All Scenarios" tab on the left:



Testing Your Integromat Scenario

Now, send another test request with the same data you used to test your webhook trigger in Integromat before:



In the Integromat scenario, you should see your flow unrolling in real-time, and once completed you'll get a recap of its successful execution at the bottom:



Finally, if all went well you should be able to see a contact and an account created in Salesflare with the contact ID being attached to the correct account:





Done!

Note that the above is a simplistic approach. In real life situation, you would have to do this below instead and check if the contact exists in the CRM database in the first place:

For this, you will have to:

• Retrieve the contact from the CRM database
• Add a router to create 2 routes.
• Use one filter on each route checking the contact email and its job role
• If the contact doesn't exist, create it and attach it to an account.
• If the contact does exist but changed its job role, update the contact ID









Additionally, you could create another route in the case the contact change company too.

Here you would use another filter:

• If the contact social profile equals to TexAu LinkedIn profile
• Account ID Name is not equal to TexAu LinkedIn Company Name



• Then after that, if the condition is matched, you will retrieve the account if it exists using another filter.
• If that account exists you will create the account.
• Then update the contact ID with newly created account details.



So many things you can do, welcome to the world of automation!