Basin and Custobar Integration

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

Keep Basin and Custobar matched by integrating their events and actions. When marketing events happen in Basin, update the Custobar 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 Custobar

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

  • Custobar

    • Marketing
    • 3 triggers
    • 4 searches
    • 6 actions

    Customer data platform for retail, with unified profiles, segments and campaigns.[6]

How to connect Basin to Custobar

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

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

WEXTL exposes actions and triggers for Basin and Custobar 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 triggersCustobar 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.

Custobar modules

  • Get Campaign Statistics Returns Custobar campaigns with their Stats, Kind, State and Utm campaign. Add a Limit if you only want the first few campaigns.
  • Import Customers Uploads people from Customers to Custobar, identified by External ID. Add Email, Phone Number, Date Joined or Mailing Lists as you have them. The Run ID of the import is returned.
  • Import Events Records customer activity from Events, each given an Event Type and Date. Match an event to a person by Customer ID, Customer Token or Email, and add UTM Campaign or Product ID for context. Output is a Run ID.
  • Import Products Sends items from Products to Custobar. Fill in a Title, Price, SKU and Stock for each item, and turn on Exclude from Recommendations to keep it out of recommendation sets. Output is the Run ID.
  • Import Sales Uploads sales to Custobar as one row per line item, with a Sale External ID, Sale Date, Currency, Product ID, Quantity and Unit Price. Add Customer Email to tie a row to a buyer. Returns the Run ID.
  • Import Shops Sends stores from Shops to Custobar. Give each an External ID, then add a Name, Shop Type, Street Address and City. Turn on Is Hidden to hide a store. You get a Run ID back.
  • List Customers Finds customers in Custobar and returns External ID, Email, Phone number and First name for each. Add a Limit for a smaller sample, and read Can email to see who accepts email.
  • List Events Retrieves recorded events from Custobar with their Type, Date, Customer ID, Email and Product ID. Enter a Limit to end the search after a chosen count.
  • List Products Shows products in Custobar, giving the External ID, Price, Category, Brand and Sku of each. A Limit shortens the result when you only need a few.
  • Make an API Call Sends a free-form request to the Custobar REST API, signed with your saved credential.
  • Watch Customers Polls Custobar on a schedule for customers and starts a run for each, with its External ID, Email and First name. Set Limit for the most customers one execution cycle works through.
  • Watch Events Checks Custobar for events at each scheduled run and outputs every one with its Type, Date and Customer ID. Enter a Limit for the cap on events handled in one execution cycle.
  • Watch Products Runs on a schedule and outputs products found in Custobar, each with its Price, Category and Brand. Use Limit to bound how many products one execution cycle processes.

Explore alternative integrations

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

Automate Basin and Custobar on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Basin and Custobar.

How do I connect Basin and Custobar?

Connect your Basin and Custobar 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 Custobar?

Example: when the "Watch New Submissions" trigger in Basin fires, WEXTL can "Get Campaign Statistics" in Custobar. Basin has 1 trigger (including Watch New Submissions). Custobar has 10 actions (including Get Campaign Statistics, Import Customers, and Import Events). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Basin and Custobar, or get started