FAQ – Sending leads via the Blastform API
🔎 General questions
Q: What's the difference between Make and Zapier?
A: Zapier: easier to get started with, intuitive interface, over 5,000 integrations.
Make: more powerful, supports complex scenarios, flow visualization, and provides better value for the money.
👉 Advice : start with Zapier if you're a beginner, move to Make for more advanced needs.
Q: Can I send my leads to several destinations at the same time?
A: Directly via the interface: no (only one URL possible).
Via Make/Zapier: yes → receive on a webhook, then distribute to several tools.
Via a proprietary API: your API can redistribute the data.
Q: Is the data sent in real time?
A: Yes. As soon as a form is submitted, delivery is near-instant (often < 1 second).
Q: What happens if the sending fails?
A: The data remains in the forms database.
Check the logs to identify the problem.
Some tools (Make/Zapier) store data and allow it to be resent.
Q: How many fields can I map?
A: As many as you need! Add as many mappings as you like (address, company, message, etc.).
⚙️ Technical questions
Q: What is "Bearer Authentication"?
A: A standard method for securing APIs. Your key is sent in the HTTP headers:
Authorization: Bearer your_secret_key
It's the equivalent of a password.
Q: Why do my JSON field names have to be exact?
A: Because APIs are case-sensitive.
Examples:
name ≠ Name ≠ NAME
email ≠ Email
👉 Always check the API documentation.
Q: What is the difference between a Bearer key and a body key?
A: Bearer key : sent in the headers (secure, standard).
Body key : sent in the JSON body (less secure).
👉 In 95% of cases, only use the Bearer key.
Q: Can I transform the data before sending?
A: Not via the interface. With Make/Zapier: yes (formatter, parser, etc.).
With proprietary API: manage it server-side.
Q: How can I test my configuration without polluting the database?
A: Use fictitious data (name="TEST", email="test@test.com").
Check that the data is arriving correctly.
Then delete them.
🟣 Questions about Make
Q: My Make URL doesn't work.
A: Check that:
✅ The webhook is activated.
✅ The URL is complete.
✅ The scenario is ON.
✅ You've done a test send.
Q: How can I see if Make has received the data?
A: In your scenario → tab Historical (clock icon) → all executions and data received appear there.
Q: Make is asking me to pay even though I'm just starting out.
A: The free plan includes 1,000 operations/month. Beyond that: subscription ≈ €9/month.
🟠 Questions about Zapier
Q: I can't find my Zapier webhook.
A: In Zapier → Create a new Zap → Trigger: Webhooks by Zapier → Catch Hook → The URL appears.
Q: Zapier says "Waiting for data".
A: Normal! Send a test form → the data will appear.
Q: What's the difference between "Catch Hook" and "Catch Raw Hook"?
A: Catch Hook : automatically parses the JSON (recommended).
Catch Raw Hook : sends the raw data (for advanced users).
👉 Use Catch Hook in 99% of cases.
🛠️ Questions about proprietary APIs
Q: My developer is asking me for the "payload" – what's that?
A: The JSON content sent.
Example:
{
"Name": "Dupont",
“email”: “contact@example.com”,
“mobile_phone”: “+33612345678”
}
Q: My API returns a 401 error but my key is correct.
A: Check that:
- No spaces before or after the key.
- The key has not expired.
- The API does expect Bearer and not another type.
- You have the necessary permissions.
Q: How can I find out which JSON names my API expects?
A: – Consult your API documentation. – Ask your developer. – Analyze a sample request. – Test with Postman.
🔒 Safety issues
Q: Is my data secure?
A: Yes, if you use HTTPS. The data is encrypted.
Precautions: – Never share your webhook URLs or secret keys. – Use keys with limited permissions. – Regenerate keys or URLs if they are compromised.
Q: Can someone intercept my data?
A: Very difficult with HTTPS.
The real risks: – Accidental sharing of webhook URLs. – Compromising a secret key. – Unauthorized access to Make/Zapier.
Q: Do I need to regenerate my webhook URL regularly?
A: No, except in case of a compromise or a team change.
📊 Questions about limits and capabilities
Q: How many leads can I send per day?
A: – Make: limited according to the plan (1,000 operations/month free). – Zapier: limited according to the plan (100 tasks/month free). – Proprietary API: depends on your server.
Q: Is there a delay between submission and sending?
A: Normally not (instant dispatch). If a delay is observed, check the recipient's performance or the logs.
Q : Can I send files (attachments)?
A: It depends on the form and the destination API. Check with your developer.
🚑 Quick troubleshooting
Q: Nothing happens when I submit the form.
A: Checklist: - ✅ URL filled in correctly? - ✅ Mapping configured? - ✅ Webhook/API enabled? - ✅ Logs checked? - ✅ Tested with Postman?
Q: The data is coming through, but some fields are empty.
A: Check: - Accuracy of JSON names (case-sensitive). - Fields filled in correctly in the form. - Correct mapping.
Q: I've configured everything, but I want to start again.
A: - Remove mappings (❌). - Change URL if necessary. - Recreate step by step. - Test again.