We don’t yet have FLG 360 listed as a service in Zapier. They require us to publicly publish the API docs, which we’re in the process of doing.
Until then, it’s fairly easy to connect service -> FLG 360 with Zapier’s webhooks, and vice versa. In this tutorial, we’ll connect email -> FLG 360. That’s not so useful, but by replacing email with any of Zapier’s other ~250 services, it becomes very useful.
In Zapier, create a new Zap:
Choose ‘Email’ (New Inbound Email) as the trigger, and ‘Web Hook’ (POST) as the action.
Next, you’ll see a couple of options which Zapier will tell you are all set, just move on.
Now, choose an email address that you’ll use to trigger this Zap. We’re choosing ‘flg360′ as the email address prefix. It can be anything you want.
Next, you’ll need to head over to FLG 360, and go to ‘Tools’, then ‘Capture Leads’, and select ‘From a Website’. You should see a screen like this:
This is the trickiest part (but don’t worry, it’s not too bad). Find the URL inside
<form action="">, it should be like this but with your account’s subdomain:
Paste this into the ‘URL’ field in Zapier. Then you need to fill out the ‘Data’ box in Zapier with the other fields in your form that you want to send through.
You’ll at least need:
intLeadGroupID|(The lead group ID)
strLeadFirstName|(The first name)
strLeadLastName|(The last name)
These three fields are always required. But you might want to add other fields you can see in the form such as strLeadEmail or strLeadData1.
Pay attention to the optional/required settings in your lead group, and the field types for any additional fields. The data you get from your action will of course need to be compatible with your lead group’s restraints.
We’re using these settings (assuming our lead group ID is 12345):
Click the ‘Insert Fields’ button to insert a field that comes from the action. In our example, we’re using the email’s subject as the first name, and the email sender as the lead’s email address. You might find that the mappings are more obvious when you link a more relevant service to FLG 360. We’re kind of fudging the mapping for the purposes of this demo. After you’ve tested the Zap, you’ll see samples too when you insert fields which makes things easier.
The final step is to test and make the Zap live, which happens over the next few steps.
You should then be live!
It’s also possible to do this the other way round, going from FLG 360 -> service by making the trigger in Zapier a webhook, and adding a webhook lead type action in FLG 360 when you want to trigger the Zap.