Skip to main content
Estimated reading: 8 minutes 135 views

Sender Integration as an Action

Sender is an email and SMS marketing platform. Your subscribers live there, along with the groups you use to segment them and the automations you send them.

Every integration in Bit Integrations has two halves. The trigger is what starts it, such as a Forms submission or a WooCommerce order. The action is what happens next. When Sender is your action, the result is a subscriber created, updated, moved between groups, or removed, built from whatever data your trigger sent in.

In practice, this replaces the CSV export. Someone fills in a form on your WordPress site, and they are in your Sender list seconds later, in the right group, with no manual step in between.

Action eventWhen to use it
Create or Update SubscriberAdds a new subscriber, or updates the details of one who already exists. The safest default for form submissions, since a repeat sign-up refreshes the record instead of creating a duplicate.
Update SubscriberChanges the details of an existing subscriber only. Use it when you want to enrich a contact you know is already in Sender, such as adding a phone number after a later form.
Delete SubscriberRemoves a subscriber from your Sender account entirely. Useful for handling deletion requests automatically.
Remove Phone From SubscriberClears the phone number from a subscriber record while keeping the contact. Good for SMS opt-out workflows where the person still wants emails.
Add Subscriber To GroupPuts an existing subscriber into a group you choose. Use it to segment people based on what they did, such as which form they filled in.
Remove Subscriber From GroupTakes a subscriber out of a group. Handy for moving people between segments, for example removing them from a “Free trial” group once they buy.
Create GroupCreates a new group in your Sender account. Useful when each incoming record needs its own segment, such as one group per event or per client.
Update GroupRenames or edits an existing group. A tidy-up action rather than an everyday one.
Delete GroupRemoves a group from your Sender account. Use it to clean up segments you no longer need.

Step-by-step: Sender Integration as an Action

There are four steps. The only fiddly part is generating an API token in Sender, and that is a five-click job once you know where the button lives.

Step 1: Create an integration and pick your trigger

An action needs a starting point, so the trigger comes first.

  • Open Bit Integrations from your WordPress dashboard.
  • Click Create Integration.
  • Search for and select the plugin or app you want to pull data from, such as Gravity Forms, WPForms, Fluent Forms, WooCommerce, Elementor Form, or any other form you use.
  • Complete that trigger’s short setup so Bit Integrations knows which fields are coming in.

Bit Integrations then takes you to the action selection page. Type “Sender” into the search box and click the Sender card.

Step 2: Create your Sender API token

Bit Integrations connects to Sender with a Bearer API token. You generate that inside your Sender account, so open Sender in a new browser tab and follow these five short steps.

1. Open Account settings

From your Sender dashboard, click Account settings at the bottom of the left sidebar.

2. Open API access tokens

In the settings sidebar, click API access tokens.

3. Click Create API token

On the API access tokens page, click the orange Create API token button in the top right corner.

4. Choose how long the token stays valid

A small window asks how long the token should last. Choose Forever if you want the connection to keep working indefinitely, or pick a shorter period if your team prefers to rotate credentials. Then click Create.

Worth knowing: If you set an expiry date instead of Forever, your integration will stop working the day the token expires. Make a note of the date and generate a fresh token before then; otherwise, subscribers will quietly stop syncing.

5. Copy the token

The sender generates the token and adds it to the top of the list. Click Copy token beside it, or click the eye icon first if you want to see the value. Keep this tab open until the connection is working.

Keep it private: An API token works like a password for your Sender account. Do not paste it into emails, screenshots, support tickets, or public documents. If it ever leaks, delete that token in Sender and create a new one.

Step 3: Authorize Sender in Bit Integrations

Go back to your Bit Integrations tab, where the Sender integration settings are waiting.

  • Enter an Integration Name at the top. This is the label you will see in your Bit Integrations dashboard, so something like “Newsletter sign-ups” is easier to find later than the default.
  • Open the Sender Connections dropdown and choose + Add new connection.
  • Enter a Connection Name. This is just a label for the credential itself, so something like “Sender main account” works well.
  • Paste your token into the Bearer Token box.
  • Click Authorize.

Once Bit Integrations confirms the connection, click Next. You only need to do this once. The saved connection then appears in the Sender Connections dropdown, so you can reuse it for every future Sender integration on this site instead of pasting the token again.

Step 4: Choose your action event and map the fields

This is the main configuration screen. Work down it from top to bottom.

Pick the action event

Open the Action dropdown and choose what should happen: Create or Update Subscriber, Update Subscriber, Delete Subscriber, Remove Phone From Subscriber, Add Subscriber To Group, Remove Subscriber From Group, Create Group, Update Group, or Delete Group. The fields below change to suit your choice.

If you pick one of the group events, you will also be asked to select which group the action applies to.

Map your fields

The Map Fields area has two columns. On the left are your trigger fields, meaning the data coming in from your form or app. On the right are the Sender fields that data will fill, such as Email, First Name, and Phone. Pair them up so each piece of information lands in the right place.

Email is the field that matters most, since Sender uses it to identify each subscriber. Use the plus icon to add another row, the trash icon to remove one, and the small refresh icon beside Map Fields if your Sender field list looks out of date.

Utilities (optional)

  • Groups. Tick this to add the subscriber to one or more groups as they are created. This is how you segment people by which form they used or what they bought.
  • Trigger Automation. Tick this to start the automations attached to the selected groups. Useful when a sign-up should immediately begin a welcome sequence.

Conditional Logics (optional)

Switch this on if the action should only run in certain cases, for example, only subscribing people who ticked a marketing consent box on your form. Leave it off and the action runs every time your trigger fires.

When everything looks right, click Next to save and finish the integration.

Your automation is now live. Submit one real entry through your trigger, then open Subscribers in Sender and confirm the contact appeared with the right details and in the right group. If a field came through empty, go back into the integration and check that mapping row.

5 useful Sender integration use cases

Because Sender sits at the destination end, the interesting part is what you connect to it. Here are five pairings that solve real list-building problems.

1. Gravity Forms Sender integration

Push every Gravity Forms newsletter sign-up straight into Sender as a subscriber. Map the email, first name, and phone fields, then use the Groups utility so people land in the right segment based on which form they filled in.

2. WooCommerce Sender integration

Add customers to Sender the moment they place an order. Because Sender handles both email and SMS, you can capture the phone number at checkout and follow up with delivery updates or a post-purchase offer without exporting anything.

3. WPForms Sender integration

Turn a simple WPForms contact or lead form into a growing mailing list. Use Create or Update Subscriber so a returning visitor updates their existing record rather than creating a second one.

4. Fluent Forms Sender integration

Collect event registrations or webinar sign-ups through Fluent Forms and drop each attendee into a dedicated Sender group. Switch on Trigger Automation, and your reminder sequence starts on its own.

5. Elementor Form Sender integration

Connect an Elementor Form on your landing page directly to Sender. Visitors subscribe from the page they are already on, and the contact appears in your Sender dashboard within seconds, correctly grouped and ready for your next campaign.

These are only examples. Bit Integrations connects Sender to a long list of form builders, e-commerce plugins, CRMs, and other apps, so you can build whichever combination fits your marketing workflow.

Share this Doc

Sender Integration as an Action

Or copy link

CONTENTS
Bit Integrations footer logo
Connect WordPress to Every Tool You Already Use
logo list

Subscribe

×
Cancel