Acumbamail
Acumbamail is an email marketing platform popular in Spain and Latin America. Advanced Form Integration adds form submissions to your Acumbamail mailing lists as new subscribers, so every newsletter signup, lead capture, or registration form on your WordPress site grows your audience automatically.
What you’ll need
- An active Acumbamail account.
- An Acumbamail API Key (see below).
- The Advanced Form Integration plugin installed and activated.
Get your Acumbamail API key
Acumbamail authenticates API requests with an auth token passed in the request body.
- Sign in to your Acumbamail account.
- Go to your account settings and locate the API section.
- Copy your API Key (auth token).
Connect Acumbamail to AFI
- In WordPress, go to AFI → Settings and open the Acumbamail tab.
- Click Add New Account and paste the API Key.
- Give the account a name you will recognise.
- Click Save.
Create the integration
- Go to AFI → Add New.
- Give the integration a name, for example
Newsletter signup to Acumbamail. - Under Trigger, pick the form plugin and the specific form you want to listen on.
- Under Action → Platform, select Acumbamail.
- In Task, choose Add Subscriber.
- Pick the saved account in the Acumbamail Account dropdown.
- Pick the Mailing List to subscribe to. AFI loads your lists automatically from the API via
getLists/. - Map your form fields onto the Acumbamail fields listed below.
- Optional: open Conditional Logic to limit which submissions are sent.
- Click Save Integration.
Tasks supported
Add Subscriber
Adds the form submitter as a subscriber on the chosen mailing list via POST /addSubscriber/. The API call sends list_id, welcome_email: 1, update_subscriber: 1, and the mapped fields as merge_fields. Existing subscribers with the same email are updated rather than duplicated.
| Field | Field key | Required | Notes |
|---|---|---|---|
email |
Yes | Subscriber email address | |
| Name | name |
No | Subscriber first name |
| Surname | surname |
No | Subscriber last name |
| Double Opt-in | double_optin |
No | Set to true to send a confirmation email before subscribing. Defaults to false (immediate subscription). |
Any other fields you add to the mapper are passed as custom merge fields in the merge_fields object. The field keys must match the field names configured in your Acumbamail list.
Default behaviors
- Welcome email: always sent (
welcome_email: 1in the API call). - Update existing: if the email already exists on the list, the subscriber’s fields are updated (
update_subscriber: 1). - Double opt-in: disabled by default. Enable it by mapping a
truevalue to thedouble_optinfield if your form has a consent checkbox or if compliance requires confirmed opt-in.
Conditional logic example
Only subscribe contacts to your “Promotions” list when the form’s marketing_consent checkbox is checked. Submitters without consent are not added to Acumbamail. Add a condition: Marketing Consent is Yes.
Troubleshooting
Nothing arrives in Acumbamail
Open AFI → Log and find the most recent entry for this integration. AFI stores the request it sent and the raw response it got back, so the Acumbamail error message is right there. If there is no log entry at all, the trigger never fired: re-check the form selection and submit a real test entry from the front end rather than the form builder preview.
API key rejected
Copy the API key directly from your Acumbamail account settings with no leading or trailing spaces. If the key was regenerated in Acumbamail, update it in AFI → Settings → Acumbamail.
Custom fields not populating
Custom fields are passed as merge fields using the exact key name you map. The key must match the field name configured in your Acumbamail list (under Lists → list settings → Custom Fields). If the key does not match, Acumbamail silently ignores the value.
Mailing list dropdown is empty
AFI loads your lists from the getLists/ endpoint after you select an account. If the dropdown is empty, verify the API key is correct and that you have at least one list created in Acumbamail.