Skip to content
Gaurav TiwariDocs

Sender Integration

Version 4.15.1 Updated November 16, 2026

Add to Sender adds a subscriber to Sender (sender.net), or updates an existing one, and assigns them to Sender groups. It talks to Sender’s API directly and needs no other WordPress plugin.

Action type: sender

Setup

  1. In Sender, create an API access token in your account settings.
  2. Open your form’s Actions tab and choose Add to Sender under Marketing & CRM.
  3. Paste the token into API access token. The field masks it.
  4. Optionally enter Group IDs, separated by commas, such as eZVD4w, b2vAR1. Use the IDs, not the group names.
  5. Choose your form’s Email field. Optionally map first name, last name and phone.
  6. Add Sender custom fields as a JSON object if you use them, for example {"company":"[company]"}.
  7. Choose whether new and updated subscribers start matching Sender automations.
  8. Save the form. Use Test action with your own address when ready. It makes a real request and creates a real subscriber.
Add to Sender action settings with API access token, group IDs, email field and optional name, phone and custom fields

Settings Reference

SettingRequiredDefaultDescription
API access tokenYes—Sent as Authorization: Bearer <token>
Group IDsNo—Comma-separated Sender group IDs
Email fieldYesemailForm field holding the subscriber’s email
First name fieldNo—Sent as firstname
Last name fieldNo—Sent as lastname
Phone fieldNo—Sent as phone. Sender expects a country code, such as +49
Custom fields (JSON)No—Sender custom fields; values can use form variables
AutomationsNoStartSent as trigger_automation

Behavior

  • The action sends POST https://api.sender.net/v2/subscribers with the email, the mapped fields, the groups and trigger_automation.
  • Sender doesn’t document what its create endpoint does with an email that already exists. When Sender rejects the create with HTTP 400, 409 or 422, the action updates the subscriber by email (PATCH /v2/subscribers/{email}) and adds them to each group with POST /v2/subscribers/groups/{groupId}. If no subscriber has that email, the original rejection is reported.
  • Existing subscribers keep their current groups. The action only adds the groups you list.
  • Custom field keys can be the plain field name (company) or Sender’s merge form ({$company}). Both are sent as {$company}. Checkbox values are joined with commas.
  • Empty optional mappings leave the subscriber’s existing values alone.
  • HTTP failures and "success": false responses are failures in Core Forms. Rate limits (HTTP 429) and server errors can be retried by the shared retry queue, using Sender’s Retry-After header. Error messages never include the token or Sender’s response body.
  • Spam and submissions still awaiting payment don’t reach Sender.

Sender’s API adds people as active subscribers. It has no double opt-in option on this endpoint. Only send people who agreed to receive your emails. For example, add a required consent checkbox to the form, or use a condition so the action runs only when the box is ticked. This matters most for sites under the GDPR.

Add to Sender action with a condition that runs it only when the CONSENT field is not empty

Troubleshooting

  • HTTP 401: The token is wrong or was revoked. Create a new one in Sender.
  • HTTP 422 for a new subscriber: Sender rejected the data. Check the email, the phone format (country code) and the custom field names.
  • Subscriber not added to a group: Check that the group ID exists in the same Sender account as the token.
  • “Enter Sender group IDs”: Group IDs contain only letters and numbers. Remove spaces inside an ID and any group names.

Sender’s API reference documents subscribers, groups and authentication.

Share

Was this helpful?

Still stuck? Open a support ticket