Please Note: When using the LeadByte App on Zapier, a LeadByte API Key is required. You must ensure that the "Campaign -> Read" permission is enabled on the key alongside the "Lead -> Create" permission. Both permissions need to be enabled on the API Key. An admin key must be used as supplier keys do not have access to the "Campaign" permissions.
 

In our scenario, we want to set up a Zap that will receive a payload from our data collection system. The trigger type we will use will be a Zapier Webhook, using "Catch Hook".
 

On the Test section of the Zapier webhook setup, you want to copy down the hook URL and set this as the endpoint from your data collection system. 

For my example, my data collection system is PostMan and I am sending a JSON payload that would need re-formatting before it could be accepted as a lead into LeadByte.

If you send the data from your data collection system, using the hook URL as the endpoint and then click "Test trigger" back on Zapier after you have done so, this will bring up the POST you just sent.
 

Click "Continue with selected record" and then choose the "LeadByte" app.
 

Choose the action "submit a lead" and connect to your LeadByte account via the UI.
Using the API key with the permissions noted at the top of this article enabled.
 

After connecting your account, choose which campaign on the next page and then map the fields from your data collection system's payload that you want to submit into LeadByte.
 

If you would like the leads submitted through this Zap to be assigned to a specific supplier, you can set an SID value here.

Finally, you can perform a test before publishing the Zap if the lead arrives into LeadByte without issue.
 

This video below showcases how the Zapier App can be used:

This video below shows how you can use a custom webhook rather than our Zapier app.