AFI
EZ Texting
EZ Texting is a bulk SMS and text message marketing platform. Advanced Form Integration adds contacts to your EZ Texting account from WordPress form submissions, so every sign-up or lead capture can be enrolled in your SMS campaigns.
What you’ll need
- An active EZ Texting account.
- An EZ Texting App Key and App Secret (see below).
- The Advanced Form Integration plugin installed and activated.
Get your EZ Texting API credentials
EZ Texting uses an App Key / App Secret pair that AFI exchanges for a temporary access token via a.eztexting.com/v1/tokens/create. The token is cached until expiry and automatically refreshed.
- Sign in to your EZ Texting account.
- Open your Profile → API settings.
- Create an App Key / App Secret pair and copy both values.
- In WordPress, go to AFI → Settings → EZ Texting.
- Click Add Account, paste the App Key and App Secret, and give the account a name.
- Click Save.
Create the integration
- Go to AFI → Add New.
- Give the integration a name, for example
SMS signup to EZ Texting. - Under Trigger, pick the form plugin and the specific form.
- Under Action → Platform, select EZ Texting.
- In Task, choose Create Contact.
- Pick the saved account in the EZ Texting Account dropdown.
- Map your form fields onto the EZ Texting fields listed below.
- Optional: open Conditional Logic to limit which submissions are sent.
- Click Save Integration.
Tasks supported
Create Contact
Creates a contact via POST /v1/contacts on api.eztexting.com. The phone number is required. Bearer authentication is handled automatically by AFI.
| Field | Field key | Required | Notes |
|---|---|---|---|
| Phone Number | phoneNumber |
Yes | E.164 format or digits only |
| First Name | firstName |
No | |
| Last Name | lastName |
No | |
email |
No | ||
| Note | note |
No | |
| Group IDs | groupIds |
No | Comma-separated group IDs |
Pro features
The Pro integration extends the free version with a custom fields repeater and an opt-in status selector. Pro uses the same EZ Texting credential store.
Custom fields
Pro adds a table where you enter the exact custom field name configured in EZ Texting and the value or trigger tag. Custom fields are sent alongside the standard payload.
Opt-in status
Pro lets you explicitly set the contact’s opt-in status: OPT_IN (only with verified consent), OPT_OUT, or leave it to EZ Texting’s default.
Feature comparison
| Feature | Free | Pro |
|---|---|---|
| Create contact | ✅ | ✅ |
| Standard fields (name, email, phone, note, groups) | ✅ | ✅ |
| Custom fields | No | ✅ |
| Opt-in status control | No | ✅ |
Conditional logic example
Only add contacts who explicitly opted in to SMS. Add a condition on sms_consent being “yes”. Submissions without consent still go through other integrations (e.g. email only).
Troubleshooting
Token exchange fails
AFI surfaces the EZ Texting error in the log. Verify the App Key and App Secret are correct and that your EZ Texting plan includes API access.
401 on contact creation
The cached access token may have expired or been revoked. AFI automatically retries once with a fresh token on HTTP 401. If it persists, re-enter your App Key and App Secret in settings.