Elastic Email and Flowise AI Integration

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

Automate the handoff between Elastic Email and Flowise AI - your marketing events flow into ai actions on a visual canvas your team can read. Set up the workflow once with 3 simple steps in the WEXTL® builder, let AI take smart decisions between apps, and never write a line of glue code again.

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

Learn about Elastic Email and Flowise AI

Detailed info you need to know about Elastic Email and Flowise AI integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Elastic Email

    • Marketing
    • 2 triggers
    • 53 searches
    • 65 actions

    Send email, manage contacts, lists and campaigns, verify addresses and read delivery events.[5]

  • Flowise AI

    • AI
    • 2 triggers
    • 17 searches
    • 30 actions

    Low-code builder for AI agents and chatbots.[6]

How to connect Elastic Email to Flowise AI

Set up your Elastic Email and Flowise AI integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Elastic Email and Flowise AI work in WEXTL?

WEXTL exposes actions and triggers for Elastic Email and Flowise AI 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.

Elastic Email triggersFlowise AI actions

Elastic Email modules

  • Add a Domain Registers a sending Domain and shows the DNS records to configure, namely Spf, Dkim, MX and DMARC. Turn on Set As Default to make it the default.
  • Add Bounces Marks addresses from Emails as bounced so Elastic Email stops sending to them.
  • Add Complaints Records addresses from Emails as spam complainers on the Elastic Email suppression list.
  • Add Contacts Adds contacts from Contacts and can place them on Lists. Each contact comes with its Email, Status, Consent and Custom Fields.
  • Add Contacts to a List Puts contacts on a List, either by Emails or by a Rule that matches them.
  • Add or Subtract Credits Adjusts the email balance of a Sub-account by the amount of Credits. Use Notes to record why.
  • Add Unsubscribes Puts addresses from Emails on the unsubscribe list.
  • Check a Channel Export Status Reports whether a channel events export with this Export ID has finished.
  • Check a Contact Export Status Shows how far a contacts export has got, for the Export ID you started.
  • Check a Domain Restriction Looks at a sending Domain and reports a Result saying whether it is restricted.
  • Check an Events Export Status Reports whether the events export with the Export ID returned by Export Events has finished.
  • Create a Campaign Builds a campaign called Name sent From a chosen address. Attach a Template, Lists or Segments, add a Subject and Reply To, and tag links with UTM Source, UTM Medium, UTM Campaign and UTM Content.
  • Create a List Makes a mailing list called List Name. Turn on Allow Unsubscribe to permit opt-outs and fill Emails to seed it with contacts.
  • Create a Segment Saves a contact segment under a Name, defined by a Rule.
  • Create a Sub-account Opens a separate sending account from an Email and Password. Turn on Send Activation to mail the owner, and use Daily Send Limit, Max Contacts and Email Size Limit to cap usage.
  • Create a Template Saves a reusable message under a Name. Supply an HTML Body, Plain Text Body, AMP Body or CSS, and set Template Scope for who can use it.
  • Create a Webhook Registers a URL that receives event notifications under a Name. Turn on the Notification For switches such as Notification For Sent or Notification For Clicked to choose which events are sent.
  • Create an API Key Generates an access key with a Name and Access Level. Add Expires for an end date, Restrict Access To IPRange to limit callers, or a Sub-account to scope it. The new Token is returned.
  • Create an Inbound Route Sets up handling for incoming mail. Use Filter with a Filter Type to match messages, and Action to decide what happens to them.
  • Create an SMTP Credential Issues SMTP login details labelled with a Name. Set Expires to end it automatically, and a Sub-account to bind it.
  • Delete a Campaign Removes a campaign from Elastic Email.
  • Delete a Contact Deletes the contact that has this Email address.
  • Delete a Domain Deletes a sending domain from the account.
  • Delete a File Removes an uploaded File from Elastic Email storage.
  • Delete a List Removes a mailing List from Elastic Email.
  • Delete a Segment Deletes a saved audience Segment from the account.
  • Delete a Sub-account Removes a child account from your Elastic Email account.
  • Delete a Suppression Removes an address from the suppression lists by Email.
  • Delete a Template Deletes a stored message Template from the account.
  • Delete a Verification File Deletes an uploaded Verification File from the account.
  • Delete a Verification Result Deletes the stored verification result for an Email.
  • Delete a Webhook Deletes a Webhook endpoint from the account.
  • Delete an API Key Deletes an API key, optionally one that belongs to a Sub-account.
  • Delete an Inbound Route Removes an inbound mail rule from the account.
  • Delete an SMTP Credential Removes SMTP login details, optionally from a Sub-account.
  • Delete Contacts in Bulk Removes many contacts at once, selected by a Rule or a list of Emails.
  • Download a File Retrieves the content of a stored file as a Value.
  • Download Verification File Results Fetches the finished results of a bulk Verification File as a Value.
  • Export Channel Events Starts an export for one Channel. Filter with Event Types, From and To, and pick File Format, Compression Format and File Name. You receive a Link and Public Export ID.
  • Export Contacts Creates an export of contacts, optionally those matching a Rule or listed as Emails. Choose File Format, Compression Format and File Name for the output.
  • Export Events Begins an export of account events, limited by Event Types and a From to To date range. Keep the Public Export ID to follow progress.
  • Get a Campaign Retrieves a campaign with its Content, Status, Recipients and Excluded Recipients.
  • Get a Contact Looks up a contact from its Email and returns the Status, First Name, Last Name, Consent and Custom Fields.
  • Get a Domain Reads a sending Domain with its Spf, Dkim and MX records and the Validation Log.
  • Get a List Pulls a mailing List with its Public List ID, Date Added and Allow Unsubscribe setting.
  • Get a Segment Retrieves a Segment together with the Rule that defines its audience.
  • Get a Sub-account Reads a child account with its Settings, Last Activity, Email Credits and Total Emails Sent.
  • Get a Sub-account API Key Retrieves the key that lets you work as a child account, delivered as a Value.
  • Get a Suppression Checks whether an Email is suppressed and why, showing the Error Code, Friendly Error Message and Date Updated.
  • Get a Template Returns a stored Template with its Subject, Body, Template Type and Template Scope.

Flowise AI modules

  • Check Server Pings the Flowise server and returns its Pong answer. Confirms that the base URL and credential respond.
  • Create a Chatflow Creates a chatflow from a Name, optionally with Flow Data, Chatbot Config and a Category. Set Type to Chatflow or Multi Agent, and turn on Deployed or Public to mark it as deployed or public.
  • Create a Document Store Creates an empty document store called by your Name. Use Description to note what the store holds.
  • Create a Lead Captures contact details from a conversation in a Chatflow, storing Name, Email and Phone for a visitor next to the Chat ID.
  • Create a Tool Defines a tool for chatflows to call, from a Name with an optional Schema and Function. Use Color and Icon URL to give it a look.
  • Create a Variable Stores a named Variable in Flowise from a Name and Value. Use Type to say how the value is treated.
  • Create an Assistant Registers an assistant in Flowise from its Details. Add a Credential ID to link a credential and an Icon URL for its avatar.
  • Create Chat Feedback Records a Thumbs Up or Thumbs Down Rating on one Message ID of a Chat ID in a Chatflow, with optional Content text explaining it.
  • Delete a Chatflow Removes a chatflow from your instance and reports a Success flag.
  • Delete a Document Chunk Removes a single chunk of text from one loader of a Document Store.
  • Delete a Document Loader Deletes one loader from a Document Store by Loader ID.
  • Delete a Document Store Deletes a whole document store and confirms with Success.
  • Delete a Tool Deletes one custom tool from your Flowise account.
  • Delete a Variable Removes a stored variable from Flowise.
  • Delete an Assistant Deletes an assistant from Flowise. Turn on Also Delete on OpenAI to remove the OpenAI copy too.
  • Delete Chat Messages Deletes messages of a chatflow, narrowed by Chat ID, Session ID, Start Date and End Date. Turn on Hard Delete to also clear the session memory and Delete Everything to remove every message when no Chat ID, Session ID or date is given.
  • Delete Upsert History Removes upsert history entries from a chatflow, for the Record IDs listed.
  • Delete Vector Store Data Clears the vectors held by the store connected to a document store, which works for data upserted with a Record Manager.
  • Get a Chatflow Reads a chatflow with its Flow Data, Deployed flag and Chatbot Config.
  • Get a Chatflow by API Key Finds the one chatflow that belongs to a Flow API Key, returning its Flow Data and Chatbot Config.
  • Get a Document Store Reads a document store together with its Loaders, Where Used and Status.
  • Get a Tool Fetches a tool, with its Schema, Color and Description.
  • Get an Assistant Fetches one assistant with its Details, Credential, icon source and created and updated dates.
  • List Assistants Shows the assistants in Flowise with their Details and Credential, capped by Limit.
  • List Chat Feedback Shows feedback left on the messages of a Chatflow. Filter with Chat ID, Start Date and End Date, sort with Order, and bound the result with Limit.
  • List Chat Messages Shows messages of one chatflow. Narrow them by Session ID, Chat Type, Start Date and End Date, or by Feedback Type, and use Order for newest or oldest first.
  • List Chatflows Returns your Flowise chatflows, flagging which are Deployed and which Is Public, capped by Limit.
  • List Document Chunks Pages through the chunks of a loader in a Document Store, each with Page Content and Metadata. Give the Loader ID, then move through the pages with Page and Limit.
  • List Document Stores Retrieves document stores along with their Status and Where Used, capped by Limit.
  • List Leads Shows the leads captured through a chatflow with their Name, Email and Phone, capped by Limit.
  • List Tools Gets custom tools with their Description and Schema, capped by Limit.
  • List Upsert History Gets the upsert runs of a Chatflow with each Result and Date. Narrow by Start Date and End Date, reorder with Order, and set the Limit.
  • List Variables Gets the variables stored in Flowise, capped by Limit. Turn on Include Values to read their values as well.
  • Make an API Call Makes an authorized free-form request to the Flowise AI REST API with your saved credential.
  • Query a Vector Store Runs a similarity search with your Query against the vector store behind a document store. You get the matching Docs plus Time Taken.
  • Refresh a Document Store Re-runs the loaders of a document store to sync its data with the sources. Use Items to limit the refresh to chosen loaders and read Num Added, Num Updated, Num Deleted and Num Skipped.
  • Send a Message to a Chatflow Sends a Message to a chatflow and returns its answer as Text, with the Chat ID and Session ID. Pass History to replay earlier turns, or Override Config for a one-off run.
  • Update a Chatflow Renames a chatflow through Name, swaps its Flow Data or Chatbot Config, and flips Deployed and Public. Use Clear Fields to empty the API Key ID, Chatbot Config or API Config.
  • Update a Document Chunk Rewrites the Content of one chunk in a loader of a Document Store, and optionally its Metadata.
  • Update a Document Store Renames a Document Store with Name and rewrites its Description. Select Description under Clear Fields to empty it.
  • Update a Tool Rewrites a tool by its Name, Description, Schema and Function. Use Clear Fields to blank the Description, Color or Icon URL.
  • Update a Variable Replaces the Value stored for a variable, and optionally renames it with Name or switches its Type.
  • Update an Assistant Edits an assistant by rewriting its Details, Credential ID or Icon URL. Use Clear Fields to remove the avatar.
  • Update Chat Feedback Changes the Rating and Content of an existing feedback entry with this Feedback ID.
  • Upload Chat Attachments Attaches a File to a chat of a chatflow, saved under a File Name with its extension. Turn on Return Base64 to get the content inline as base64 text, and set the Chat ID of the session.
  • Upsert a Document Pushes a File through your chosen Loader, Splitter, Embedding and Vector Store of a document store. Turn on Replace Existing to overwrite earlier versions, or Create New Store to make a store in the same call.
  • Upsert Vectors Upserts a File into the vector store of a chatflow. Set Stop Node ID to end the run at a chosen node, and Override Config to adjust settings for it.
  • Watch New Chat Feedback Triggers once per new feedback entry on a chatflow, polled periodically. Use Limit to cap how many are read at each check.
  • Watch New Chat Messages Runs the workflow for each new message in a chosen chatflow, checking on a schedule. Set Chat Type to Internal or External to filter, and Limit to cap each check.

Explore alternative integrations

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

Automate Elastic Email and Flowise AI on WEXTL®

Claim your 3-day trial to build Elastic Email with Flowise AI integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Elastic Email and Flowise AI.

How do I connect Elastic Email and Flowise AI?

Connect your Elastic Email and Flowise AI 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 Elastic Email and Flowise AI?

Example: when the "Watch Delivery Events" trigger in Elastic Email fires, WEXTL can "Check Server" in Flowise AI. Elastic Email has 2 triggers (including Watch Delivery Events and Watch Notifications). Flowise AI has 47 actions (including Check Server, Create a Chatflow, and Create a Document Store). Add filters and transforms between steps when you need them.[1]

Can Elastic Email trigger actions in Flowise AI, and Flowise AI in Elastic Email?

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 Elastic Email and Flowise AI?

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

Does Elastic Email integrate with Flowise AI in real time?

Yes. Trigger-based automations start the moment Elastic Email (or Flowise AI) 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 Elastic Email + Flowise AI 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 Elastic Email with Flowise AI?

You can build your Elastic Email + Flowise AI automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Elastic Email and Flowise AI integration.

  1. Elastic Email and Flowise AI integration source code, module specs and credentials implementation.
  2. Our Elastic Email and Flowise AI integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Elastic Email and Flowise AI, 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. Elastic Email integration information
  6. Flowise AI integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore Elastic Email and Flowise AI, or get started