Basin and Customer.io Integration

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

Keep Basin and Customer.io matched by integrating their events and actions. When marketing events happen in Basin, update the Customer.io automatically - without any line of code in visual workflow builder.

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

Learn about Basin and Customer.io

Detailed info you need to know about Basin and Customer.io 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]

  • Customer.io

    • Marketing
    • 2 triggers
    • 71 searches
    • 41 actions

    Messaging automation with profiles, segments, campaigns, sends and reporting webhooks.[6]

How to connect Basin to Customer.io

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

How does the integration between Basin and Customer.io work in WEXTL?

WEXTL exposes actions and triggers for Basin and Customer.io 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 triggersCustomer.io 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.

Customer.io modules

  • Add Segment Members Adds the customers listed to a segment by their identifiers. Use ID Type to say whether those identifiers are ids, emails or Customer.io ids.
  • Create a Newsletter Creates a newsletter in one of six channels, with the people matched by Recipients as its audience. Fill Subject and Body for the content, and set Scheduled At or turn on Send Now to send it. Returns the ID and Name of the new newsletter.
  • Create a Newsletter Test Group Adds an A/B test group to a newsletter. Output includes the ID and Content IDs.
  • Create a Newsletter Test Group Translation Adds a language version to an A/B test group. Set Language to an IETF code such as fr, es or pt, and translate the Subject or Body.
  • Create a Newsletter Translation Translates a newsletter into another language. Give a Language code such as fr, es or pt, then a Subject, Body or Preheader Text.
  • Create a Segment Creates a segment under a Name, with an optional Description that helps people recognize its purpose. Output includes the ID, State and Progress.
  • Create a Snippet Stores a reusable snippet under a unique Name of up to 150 characters. Fill the Value with plain text or Liquid. The Updated At time is returned.
  • Delete a Customer Deletes a customer profile addressed by Customer Identifier, which accepts an id, an email or a Customer.io id.
  • Delete a Newsletter Removes a single newsletter from your Customer.io workspace.
  • Delete a Newsletter Test Group Translation Deletes one Language from an A/B test group. The default language variant cannot be deleted.
  • Delete a Newsletter Translation Removes the translation named by Language from a newsletter. The default language variant cannot be removed.
  • Delete a Segment Deletes a segment, found by its ID, from Customer.io.
  • Delete a Snippet Removes a snippet from your workspace and returns Success.
  • Download an Export Downloads the data of an export, ready to pass to later steps.
  • Export Customer Data Starts an export of customers that match Filters. Name the Attributes to include, or leave them out to get every attribute.
  • Export Deliveries Data Starts an export of delivery data for a Newsletter ID, Campaign ID, Transactional Message ID or Action ID. Set Start Date to limit the range.
  • Get a Broadcast Fetches a single broadcast from Customer.io and returns its ID.
  • Get a Broadcast Action Opens a single action that belongs to a broadcast, giving its ID.
  • Get a Broadcast Action Translation Fetches an action of a broadcast translated into the chosen Language. Output gives its ID.
  • Get a Campaign Retrieves a campaign from Customer.io, giving back its ID.
  • Get a Campaign Action Looks up a single action of a campaign and hands over its ID.
  • Get a Campaign Action Translation Reads the translated version of a campaign action for a Language.
  • Get a Collection Fetches one collection and returns its Name, Rows, Bytes and Schema.
  • Get a Message Reads a message record found through List Messages.
  • Get a Newsletter Fetches a newsletter with its Name, Sent At, Type, Tags and Recipient Segment IDs.
  • Get a Newsletter Test Group Translation Reads the translation of an A/B test group in one Language, including its Body, AMP Body and From.
  • Get a Newsletter Translation Fetches a newsletter translated into a Language, returning its Layout, Body and Name.
  • Get a Newsletter Variant Reads a single content variant, returning its Name, Layout, Body and Language.
  • Get a Reporting Webhook Reads the configuration of one reporting webhook from Customer.io.
  • Get a Segment Fetches a segment, returning its Name, Description, State and Progress.
  • Get a Segment Customer Count Returns how many customers sit in a segment, as Customer Count beside the Segment ID.
  • Get a Transactional Message Fetches one transactional message with its Name, Description, Link Tracking, Open Tracking and Queue Drafts settings.
  • Get a Transactional Message Translation Reads a transactional message in a two- or four-letter Language code, returning its Body, From and Reply To.
  • Get an Archived Message Reads the archived content of one message from the Customer.io workspace.
  • Get an Export Fetches an export from your workspace. Use Download an Export to get its data.
  • Get Broadcast Action Link Metrics Returns link metrics for one broadcast action, whose Action ID appears in List Broadcast Actions.
  • Get Broadcast Action Metrics Reads the metrics of one action in a broadcast. Action IDs are listed by List Broadcast Actions.
  • Get Broadcast Errors Lists the errors recorded for a broadcast trigger. Set Limit to cap how many errors are returned.
  • Get Broadcast Link Metrics Gives link metrics for a broadcast as a whole, rather than for one action.
  • Get Broadcast Messages Pages through the messages of a broadcast and returns each ID.
  • Get Broadcast Metrics Reads metrics for a broadcast and puts its ID into the output.
  • Get Broadcast Status Reads the status of a broadcast trigger, found through List Broadcast Triggers, giving its ID.
  • Get Campaign Action Link Metrics Gets link metrics for a single campaign action. Its Action ID is found in List Campaign Actions.
  • Get Campaign Action Metrics Retrieves the metrics of a single action in a campaign. Find an action to measure in List Campaign Actions.
  • Get Campaign Journey Metrics Fetches journey metrics for a campaign and puts its ID in the output.
  • Get Campaign Link Metrics Covers the links of an entire campaign, unlike Get Campaign Action Link Metrics, which covers one action.
  • Get Campaign Messages Pages through the messages of a campaign, giving the ID of each.
  • Get Campaign Metrics Provides the metrics measured for a campaign, with its ID in the output.
  • Get Collection Contents Reads the rows stored in a collection and returns them as Collection Data.
  • Get Customer Activities Looks up customer activity by Customer ID. Use ID Type to say whether that value is an ID, Email, Phone or CIO ID, narrow by Activity Type, and continue from a Page Token.

Explore alternative integrations

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

Automate Basin and Customer.io on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Basin and Customer.io.

How do I connect Basin and Customer.io?

Connect your Basin and Customer.io 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 Customer.io?

Example: when the "Watch New Submissions" trigger in Basin fires, WEXTL can "Add Segment Members" in Customer.io. Basin has 1 trigger (including Watch New Submissions). Customer.io has 112 actions (including Add Segment Members, Create a Newsletter, and Create a Newsletter Test Group). Add filters and transforms between steps when you need them.[1]

Can Basin trigger actions in Customer.io, and Customer.io 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 Customer.io?

No. Basin-to-Customer.io 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 Customer.io in real time?

Yes. Trigger-based automations start the moment Basin (or Customer.io) 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 + Customer.io 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 Customer.io?

You can build your Basin + Customer.io 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 Customer.io integration.

  1. Basin and Customer.io integration source code, module specs and credentials implementation.
  2. Our Basin and Customer.io integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Basin and Customer.io, 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. Customer.io 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 Customer.io integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Basin and Customer.io, or get started