What is your goal?
To automatically add new subscribers to a specific Acumbamail list whenever Whenever someone submits a Jotform, I want their details (email, name, and several custom fields like organization, country, role, trust level, quiz scores) to be automatically added or updated in my Acumbamail subscriber list.
What is the problem & what have you tried?
Hello Make Community,
I’ve been working for over a month to connect Jotform submissions to Acumbamail using Make, but I keep running into errors, and I’m stuck.
What I’ve tried:
- Built scenarios using both Webhook → HTTP and Jotform “Watch for Submission” → HTTP.
- Structured the JSON body with auth, list_id, email, name, and merge_fields.
- Tried sending the API key (auth) in the body and as a query string.
- Confirmed the list ID and API key are correct.
Error messages or input/output bundles
Errors encountered:
-
DataError: Bad Request (missing mandatory parameters like list_id or merge_fields).
-
InvalidConfigurationError: Unauthorized (even with correct API key and list ID).
-
JSON parsing errors when mapping Jotform fields (e.g., “Expected ‘,’ or ‘}’ after property value”).
Example of the JSON I’m sending:
{ “auth”: “MY_API_KEY”, “list_id”: “1228471”, “email”: “john@example.com”, “name”: “John Doe”, “merge_fields”: { “FIRSTNAME”: “John”, “LASTNAME”: “Doe”, “ORGANIZATION”: “Demo Org”, “COUNTRY”: “Nigeria”, “ROLE”: “Tester”, “TRUST_LEVEL”: “High”, “TQ_RAW”: “10”, “TRUST_PERCENTAGE”: “90” }, “update_subscriber”: 1 }
ERROR REPORT:
InvalidConfigurationError
Unauthorized
Unauthorized
Origin
HTTP
Automatic error handler
If you want to handle this error automatically, choose one of the following options. This will create a new error-handler route in your scenario. You can then expand the route in any way you like.
Input
Bundle 1Collection
URL https://acumbamail.com/api/1/addSubscriber/
Method post
HeadersArray
1Collection
Name Content-Type
Value application/json
Body content type json
Body input method jsonString
Share cookies with other HTTP modules false
Parse response true
Allow redirects true
Return error if HTTP request fails true
Body contentLong String
{
“auth”: “Acumbamail-API”,
“list_id”: “1228471”,
“email”: “john@example.com”,
“name”: “textbox_sample12 textbox_sample13”,
“merge_fields”: {
“FIRSTNAME”: “textbox_sample12”,
“LASTNAME”: “textbox_sample13”,
“ORGANIZATION”: “textbox_sample15”,
“COUNTRY”: “textbox_sample17”,
“ROLE”: “textbox_sample16”,
“TRUST_LEVEL”: “Level 1 - Trust at Risk”,
“TQ_RAW”: “9”,
“TRUST_PERCENTAGE”: “15”
},
“update_subscriber”: 1
}
Where I need help:
Should the API key (auth) be passed in the body or only in the query string?
What is the correct endpoint domain for Acumbamail accounts (acumbamail.com vs eu.acumbamail.com)?
Is the casing of merge field keys (e.g., ROLE, COUNTRY) critical, and what format does Acumbamail expect?
Has anyone successfully set up this integration — could you share a working Make scenario or JSON payload?
Any guidance or examples would be hugely appreciated. This integration is critical for my workflow, and I’d love to finally get it working.
Thanks in advance!
— Nkem
