Basin and Emarsys Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Basin and Emarsys to automate marketing workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Basin and Emarsys

Detailed info you need to know about Basin and Emarsys integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Basin

    • Marketing
    • 1 trigger
    • 13 searches
    • 18 actions

    Form backend that collects submissions, filters spam and forwards them to your tools.[5]

  • Emarsys

    • Marketing
    • 6 searches
    • 12 actions

    Marketing automation platform for managing contacts, segments, campaigns, and customer engagement data.[6]

How to connect Basin to Emarsys

Set up your Basin and Emarsys integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Basin and Emarsys work in WEXTL?

WEXTL exposes actions and triggers for Basin and Emarsys that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Basin triggersEmarsys actions

Basin modules

  • Create a Form Sets up a Basin form from a Name. Use Redirect URL to send visitors elsewhere after a submission, Notification Emails to alert your team and Autoreply to answer the submitter.
  • Create a Form Webhook Makes Basin post every submission of a Form to a web address. Set Format to choose the payload type and turn on Run for Spam to include spam-marked entries.
  • Create a Mail Template Saves a reusable email template under a Project, from its Name and raw HTML Body.
  • Create a Project Adds a project that groups forms and mail templates.
  • Delete a Form Removes a form together with all of its submissions. This cannot be undone.
  • Delete a Form Webhook Removes a webhook so submissions stop being posted to its address.
  • Delete a Mail Template Removes a saved email template from Basin.
  • Delete a Project Deletes a project. Basin does not document what happens to the forms in it.
  • Delete a Submission Deletes a single form submission, and the action cannot be undone.
  • Get a Form Reads one form to get its UUID, Timezone, Project Name and Redirect URL.
  • Get a Form View Shows one recorded visit to a form, with the Form UUID it belongs to and its Created At time.
  • Get a Form Webhook Reads a webhook with its URL, Format, Enabled state and Trigger When Spam setting.
  • Get a Mail Template Returns a template by Mail Template ID, along with the Project ID it sits in and the Body markup.
  • Get a Project Looks up one project to read its Name and when it was created or last changed.
  • Get a Submission Finds one submission by Submission ID. Returns the sender Email and Payload Params, plus flags for Spam, Read and Trash.
  • List Domains Shows the domains registered to your Basin account. Use Query to match text, Page to move through results and Limit to cap the count.
  • List Form Views Returns recorded views of your forms. Use Query to filter by id, uuid, form id or form uuid and Limit to set how many to read.
  • List Form Webhooks Gathers the webhooks configured across your forms, one item each. Use Query to narrow the set.
  • List Forms Pulls your forms, each with its Name and Project Name. Filter them by id, name, uuid or project id through Query.
  • List Mail Templates Finds the email templates of one Project. Use Page to step through them and Limit to cap how many are read.
  • List Projects Fetches your projects, each with a Name and a Created At time. Use Query to find one by text.
  • List Submissions Browses form submissions. Use Form to limit it to one form, Status and Date From to narrow the range and Order By to sort them.
  • Make an API Call Calls the Basin REST API directly with a free-form request under your saved credential.
  • Re-fire Webhooks for a Submission Sends the webhooks of one submission out again, so receivers may see it a second time.
  • Re-fire Webhooks for Several Submissions Replays webhooks for a batch of Submission IDs in a single call. Receivers may see those submissions again.
  • Submit a Form Posts an entry to a Basin form as a visitor would, with one row of Fields per value. Set Client IP to record the visitor address.
  • Update a Form Edits an existing form, such as its Name, Redirect URL, Notification Emails or spam checks. Use Clear Fields to empty a value.
  • Update a Form Webhook Edits a webhook to change its URL, switch Enabled on or off, or move it to another Form. Changing the URL of a webhook created by Watch New Submissions stops that trigger.
  • Update a Mail Template Replaces the Name or Body of a mail template. Add the ETag (If-Match) of the version you read and Basin refuses the write if it changed since.
  • Update a Project Retitles an existing project with a new Name.
  • Update a Submission Flags a submission as spam or not with Spam, as read with Read, or moves it to the trash with Trash.
  • Watch New Submissions Starts the workflow the moment Basin receives a form submission, through an instant webhook. Each run gets the Submission ID, Email and Attachments.

Emarsys modules

  • Add Contacts to a Contacts List Inserts contacts into one of your Emarsys contact lists, matching each by id, uid or an indexed custom field. Use Key ID for that match type and External IDs for the identifiers to insert.
  • Create a Changed Contacts Export Starts an export of contacts changed in a date window and returns its ID. Set Range Start, Range End, Origin and Origin ID to say when and from which platform or custom contact source, and Contact Fields to include up to 20 fields.
  • Create a Contact List Creates a contact list in Emarsys under a unique Name, optionally with a Description. Add the starting members through External IDs, matched by Key ID.
  • Create a Contact List Export Starts an export job for the contacts in one contact list and returns its ID. Use Contact Fields to choose between 1 and 20 fields, and Distribution Method to receive the file by FTP, SFTP or Email.
  • Create a Registered Contacts Export Starts an export task for registered contacts, bounded by Range Start, Range End and the Contact Fields to include. Turn on With Timestamp to add the registration timestamp, and use Notification URL to get a request when the export is ready.
  • Create Contacts Creates new contacts in Emarsys, each with the field values listed inside Contacts. Use Key ID to choose how the contacts are identified.
  • Create or Update Contacts Updates one or several contacts with the data you send for Contacts. Set Create If Not Exists to 1 to create the contacts that do not exist yet, and use Key ID to pick how they are matched.
  • Delete a Contact List Deletes an existing contact list from Emarsys.
  • Delete Contacts Deletes one or more contacts from your Emarsys account, matched by a list of Contact Identifiers (IDs).
  • Download Export Data Downloads the CSV file of a finished export, using the Export ID of the export that was requested. That export must have been started with its distribution method set to Local.
  • Get a Contact Fetches the field values of contacts that match Key Values. Use Field ID to Search Contacts by to match on id, uid or a custom field such as email.
  • Get Export Status Looks up the status of an export requested earlier. Map the Export ID from the module that created the export.
  • List Contact Lists Retrieves your Emarsys contact lists, each with its ID and Name. Use Limit to set the number of lists returned.
  • List Contacts Returns the Contact ID of each contact in one contact list. Raise or lower Limit to control the amount returned.
  • Make an API Call Makes an authorized free-form request to the Emarsys REST API with your saved credential.
  • Remove Contacts from a List Removes contacts from a contact list in Emarsys, using External IDs to list the contacts to remove and Key ID to say how each is identified.
  • Search Contacts Finds contacts whose Field ID matches a value, and adds the field chosen with Return to each result next to the contact id. Turn on Exclude Empty to leave out contacts with a blank value in that field.
  • Trigger an External Event Fires an Emarsys external event for a batch of Contacts, identified by Event ID. Use Trigger ID to deduplicate repeated sends, and Event Time to set when the event happened in Interactions.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Basin and Emarsys integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Basin and Emarsys on WEXTL®

Claim your 3-day trial to build Basin with Emarsys integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Basin and Emarsys.

How do I connect Basin and Emarsys?

Connect your Basin and Emarsys accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Basin and Emarsys?

Example: when the "Watch New Submissions" trigger in Basin fires, WEXTL can "Add Contacts to a Contacts List" in Emarsys. Basin has 1 trigger (including Watch New Submissions). Emarsys has 18 actions (including Add Contacts to a Contacts List, Create a Changed Contacts Export, and Create a Contact List). Add filters and transforms between steps when you need them.[1]

Can Basin trigger actions in Emarsys, and Emarsys in Basin?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Basin and Emarsys?

No. Basin-to-Emarsys automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Basin integrate with Emarsys in real time?

Yes. Trigger-based automations start the moment Basin (or Emarsys) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Basin + Emarsys integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Basin with Emarsys?

You can build your Basin + Emarsys automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Basin and Emarsys integration.

  1. Basin and Emarsys integration source code, module specs and credentials implementation.
  2. Our Basin and Emarsys integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Basin and Emarsys, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Basin integration information
  6. Emarsys integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Basin and Emarsys integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Basin and Emarsys, or get started