Faraday and Metabase Integration

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

Keep Faraday and Metabase matched by integrating their events and actions. When analytics events happen in Faraday, update the Metabase 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 Faraday and Metabase

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

  • Faraday

    • Analytics
    • 1 trigger
    • 62 searches
    • 87 actions

    Predictive analytics that forecasts customer behavior from your data.[5]

  • Metabase

    • Analytics
    • 1 trigger
    • 62 searches
    • 87 actions

    Run questions, manage dashboards, collections, permissions, and alert notifications in Metabase.[6]

How to connect Faraday to Metabase

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

How does the integration between Faraday and Metabase work in WEXTL?

WEXTL exposes actions and triggers for Faraday and Metabase 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.

Faraday triggersMetabase actions

Faraday modules

  • Watch Events Runs the workflow the moment Faraday sends a webhook event, passing its Type, Timestamp, Account ID, Resource Type and Resource ID.
  • Add an Upload Stores the content of File in your Faraday uploads, such as a CSV, and returns the Subpath and Size of the new upload.
  • Archive a Cohort Marks a cohort as archived and returns its Status. Use Cascade To to list dependent resource IDs that go into the archive with it.
  • Archive a Connection Archives a connection to outside data and returns its Created at time.
  • Archive a Dataset Puts a dataset into the archive. Use Cascade to All to include everything that depends on it.
  • Archive a Forecast Archives a forecast and returns its ID, Name and Status.
  • Archive a Persona Set Marks a persona set as archived. The reply shows its Name and Status.
  • Archive a Recommender Files a recommender in the archive. Use Cascade to All to bring its dependent resources along.
  • Archive a Scope Archives a scope. The Created at time is returned.
  • Archive a Stream Puts a data stream into the archive. The Status of the stream is returned.
  • Archive a Target Archives a target. Use Cascade To to list the dependent IDs that should be archived alongside it.
  • Archive a Trait Archives a trait, returning its Name together with its Account id.
  • Archive an Atlas Archives an atlas. Use Cascade to All to also archive the resources that depend on it, or Cascade To to name the dependent IDs.
  • Archive an Outcome Sets an outcome aside in the archive. Use Cascade To to list the dependent IDs that should be archived in the same step.
  • Create a Cohort Defines a cohort of people from Stream Conditions (JSON), Place Conditions (JSON), Location Conditions (JSON), Traits (JSON) or Attributes (JSON).
  • Create a Connection Saves access to an outside data system with a Name and its Options (JSON), for use by datasets, atlases and targets.
  • Create a Dataset Defines a dataset from Identity Sets (JSON) and Options (JSON), reading through a Connection when one is set. Use Output to Streams (JSON) or Output to Traits (JSON) to send records on and Privacy to pick Suppress or Delete for data handling.
  • Create a Forecast Defines a forecast on a Stream and Stream Property Name, entered through an Entry Stream with a Horizon (JSON). Use Eligible Cohort, Predictors (JSON) or Currency to refine it.
  • Create a Persona Set Splits the people of a Cohort into personas. Set Number of Clusters to control how many groups form and Clustering Dimensions (JSON) to choose what they split on.
  • Create a Recommender Builds a recommender on a Stream and its Stream Property Name, with Predictors (JSON) and an optional Preview.
  • Create a Scope Defines a scope from a Population (JSON) listing its cohorts and a Payload (JSON) listing attributes and outcomes.
  • Create a Target Adds a target for a Scope with a Representation (JSON) and Options (JSON). Narrow the output with Filter (JSON) and Limit Rows (JSON), and set a Connection to deliver it elsewhere.
  • Create a Trait Creates a trait. Use Readable Name for the friendlier name shown in reports, Statistical Type and Unit to describe it and Lookup Table (JSON) to map values.
  • Create a Webhook Endpoint Subscribes a URL to the chosen Events, so Faraday sends a call there when they fire. The new endpoint comes with its Enabled events and Status.
  • Create an Account Sets up a new Faraday account with a Name. Use Branding (JSON) to pass its branding settings as a JSON object.
  • Create an Atlas Sets up an atlas using Options (JSON) for its source type and settings. Use Output to Locations (JSON) to map your columns to location fields and Connection to read from a data system.
  • Create an Attribute Defines an attribute in a Feature Store, fed by the Value Property Name of a Stream. Use Readable Name for the friendlier name shown in reports, Category and Tier to classify it and Statistical Type or Unit to describe its values.
  • Create an Outcome Defines an outcome from the Attainment Cohort of people who reached it. Use Feature Blocklist to leave features out by name, and Eligible Cohort, Attrition Cohort, Prediction Mode or Bias Mitigation (JSON) to refine it.
  • Delete a Cohort Deletes a cohort definition made of stream, place and location conditions.
  • Delete a Connection Removes a connection to an external data system.
  • Delete a Dataset Deletes a dataset that reads its records through a connection.
  • Delete a Forecast Removes a forecast that predicts from a stream over a horizon.
  • Delete a Persona Set Removes a persona set that was clustered from a cohort.
  • Delete a Recommender Deletes a recommender built on a stream.
  • Delete a Scope Removes a scope, the population and payload definition that targets deliver.
  • Delete a Stream Deletes a stream of records from Faraday.
  • Delete a Target Removes a target defined on a scope.
  • Delete a Trait Removes a trait that holds a statistical type and unit.
  • Delete a Webhook Endpoint Removes a webhook endpoint that receives Faraday events at a URL.
  • Delete an Account Deletes an account from the Faraday platform.
  • Delete an Atlas Deletes an atlas definition from Faraday.
  • Delete an Attribute Removes an attribute from its feature store.
  • Delete an Outcome Deletes an outcome defined by an attainment cohort.
  • Delete an Upload Deletes a stored file from your Faraday uploads.
  • Download a Target CSV Downloads the output of a target as a CSV file you can pass to other modules.
  • Download an Upload Downloads a stored file from your Faraday uploads and returns it as a File.
  • Find or Create a Stream Looks up a stream and creates it when none exists, returning its record either way.
  • Force Update a Cohort Requests a fresh cohort build and reports the Cohort id.
  • Force Update a Connection Starts another run of a connection and reports Success with its Connection id.
  • Force Update a Dataset Rebuilds a dataset straight away and reports Success with the Dataset id.

Metabase modules

  • Add a User to a Permission Group Makes a user a member of a permission group in Metabase. Use Body to send the membership fields.
  • Append CSV to a Table Adds the rows of a CSV file to an existing Metabase table. Use Body to pass the request fields for the upload.
  • Archive a Segment Archives a segment stored in Metabase.
  • Create a Bookmark Bookmarks an item in Metabase for the connected user.
  • Create a Card Saves a card that holds a query and its chart settings. Use Type to make it a question, metric or model, and Collection to file it.
  • Create a Collection Starts a collection in Metabase. Use Parent Collection to nest it inside another, or Authority to mark it official.
  • Create a Comment Posts a comment on an object in Metabase, attached through its Target Type and Target ID.
  • Create a Dashboard Builds a dashboard in Metabase. Use Collection to place it among your collections and Parameters to add dashboard parameters.
  • Create a Dashboard Subscription Creates a dashboard subscription, called a pulse in the Metabase API. Use Cards to list its cards and Channels to set where it goes.
  • Create a Database Connects a database to Metabase. Use Details to pass the connection settings.
  • Create a Document Writes a document into Metabase, with its content coming from Document.
  • Create a Glossary Entry Records a glossary entry that pairs a Term with its Definition.
  • Create a Notification Builds a notification in Metabase out of a Payload Type and Payload. Use Handlers to add a Channel and Channel Type for each place it is sent.
  • Create a Permission Group Registers a new permission group in Metabase for controlling access. Use Body to describe the group.
  • Create a Segment Defines a segment in Metabase. Use Body to write out the segment definition.
  • Create a Snippet Saves a native query snippet in Metabase. Use Body to hand over the snippet content.
  • Create a Timeline Starts a timeline in Metabase, with its fields passed through Body.
  • Create a Timeline Event Records an event on a Metabase timeline, with the event fields supplied through Body.
  • Create a User Adds a user to Metabase from an Email address. Use First Name and Last Name to record who they are, and Group Memberships to place them in permission groups.
  • Create an Action Defines an action in Metabase. Use Model to attach it to one of your cards.
  • Create an API Key Generates an API key in Metabase. Use Group to place the key in a permission group.
  • Delete a Bookmark Removes a bookmark that points at an item in Metabase.
  • Delete a Card Deletes a saved card that lives in Metabase.
  • Delete a Collection Removes a collection from the Metabase instance.
  • Delete a Comment Deletes a comment attached to an object in Metabase.
  • Delete a Dashboard Deletes a dashboard stored on your Metabase instance.
  • Delete a Database Removes a connected database from Metabase.
  • Delete a Document Deletes a stored document on your Metabase instance.
  • Delete a Permission Group Deletes a permission group on your Metabase instance.
  • Delete a Timeline Removes a timeline of events from Metabase.
  • Delete a Timeline Event Deletes one event off a Metabase timeline.
  • Delete an Action Removes a saved action that Metabase stores.
  • Delete an API Key Revokes a stored API key in Metabase by deleting it.
  • Delete the Cache Configuration Removes the cache configuration stored in Metabase.
  • Disable a User Deactivates a user account on your Metabase instance.
  • Duplicate a Card Copies an existing card into a new one. Use Body to supply the details for the copy.
  • Duplicate a Dashboard Copies a dashboard into a new one, with the details of the copy coming from Body.
  • Execute a Dashboard Action Runs the action behind a card on a dashboard. Use Parameters to hand it the input values.
  • Execute an Action Runs an action in Metabase, handing it the values from Body.
  • Export Ad Hoc Query Results Runs a query that was never saved and exports the rows in the chosen Export Format. Use Body to describe the query.
  • Export Card Query Results Runs the query behind a card and exports its rows in the chosen Export Format. Use Body to add the request details.
  • Export Dashboard Card Query Results Exports the result of a card shown on a dashboard, in an Export Format such as csv, json or xlsx. Use Parameters for filter values.
  • Get a Card Returns one saved card from Metabase with its query and display options.
  • Get a Channel Opens one notification channel in Metabase to see how it is set up.
  • Get a Collection Shows a single collection of your Metabase instance.
  • Get a Dashboard Loads one dashboard from Metabase together with what it contains.
  • Get a Dashboard Subscription Reads one dashboard subscription. The Metabase API calls these pulses.
  • Get a Database Fetches one connected database, showing the details Metabase holds for it.
  • Get a Document Opens one stored document from your Metabase instance.
  • Get a Field Returns one table field known to Metabase.

Explore alternative integrations

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

Automate Faraday and Metabase on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Faraday and Metabase.

How do I connect Faraday and Metabase?

Connect your Faraday and Metabase 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 Faraday and Metabase?

Example: when the "Watch Events" trigger in Faraday fires, WEXTL can "Add a User to a Permission Group" in Metabase. Faraday has 1 trigger (including Watch Events). Metabase has 149 actions (including Add a User to a Permission Group, Append CSV to a Table, and Archive a Segment). Add filters and transforms between steps when you need them.[1]

Can Faraday trigger actions in Metabase, and Metabase in Faraday?

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 Faraday and Metabase?

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

Does Faraday integrate with Metabase in real time?

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

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

References

List of sources used to gather information about the Faraday and Metabase integration.

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

How we write our apps documentation

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

Explore Faraday and Metabase, or get started