Faraday and Ignition Reporting Integration

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

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

Detailed info you need to know about Faraday and Ignition Reporting 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]

  • Ignition Reporting

    • Analytics
    • 7 triggers
    • 8 searches
    • 1 action

    Reporting on Ignition engagements, invoices, and payments.[6]

How to connect Faraday to Ignition Reporting

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

How does the integration between Faraday and Ignition Reporting work in WEXTL?

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

Ignition Reporting modules

  • List Client Reports Returns clients from Ignition with their Manager, Partner and Email. Filter by State (Lead, Active, Inactive or Archived) or by any of the comma-separated Tags, and add Updated from to sync edits made since a previous export.
  • List Contact Reports Fetches contacts reported by Ignition, with a Position and Is signatory value on each. Turn on Primary contact or Invoice recipient to keep only those contacts, or use Client slug for a single client.
  • List Deal Reports Returns deals filtered by State (Open, Won or Lost) or Priority (Low, Medium or High). Use Client slug to focus on one client, Owner slug for one owner, and Closed from with Closed to for closing dates.
  • List Deal Stages Lists the deal stages set up in Ignition, showing the Win likelihood and Position of every stage. Use Limit to bound how many stages are returned.
  • List Invoice Reports Reports invoices dated between Date from and Date to, which default to the current month. Use Updated from to focus on invoices edited after an earlier export.
  • List Payment Reports Lists payments in Ignition, leaving out Cancelled ones unless Payment state is given. Filter by Collected from and Collected to dates, or by Invoice ID for payments tied to one invoice.
  • List Proposal Reports Retrieves proposals by State (Draft, Awaiting acceptance, Accepted, Lost, Completed or Archived). Add Accepted from and Accepted to for acceptance dates, and Tags to match any client tag.
  • List Service Reports Lists catalog services, filtered by State (Active, New or Deleted), an exact Service Group Name or a Service Origin such as Xero or CSV.
  • Make an API Call Makes an authorized free-form request to the Ignition Reporting REST API with your saved credential.
  • Watch Client Reports Runs on a schedule and emits clients added since the previous check, with their Email, Manager and Partner.
  • Watch Contact Reports Catches new contacts on each poll and passes each along, including Position and Is primary.
  • Watch Deal Reports Fires once for every new deal found by the poll, with its Stage name and Value in the output.
  • Watch Invoice Reports Polls on a schedule for new invoices and emits each one. Use Limit to cap how many a run handles.
  • Watch Payment Reports Checks for newly created payments and emits them, each with its Amount and Collection details.
  • Watch Proposal Reports Emits each proposal newly created at the time of a scheduled check, with their Contract term and Services.
  • Watch Service Reports Watches the service catalog for new entries and passes each service along, with its Price and Billing mode.

Explore alternative integrations

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

Automate Faraday and Ignition Reporting on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Faraday and Ignition Reporting.

How do I connect Faraday and Ignition Reporting?

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

Example: when the "Watch Events" trigger in Faraday fires, WEXTL can "List Client Reports" in Ignition Reporting. Faraday has 1 trigger (including Watch Events). Ignition Reporting has 9 actions (including List Client Reports, List Contact Reports, and List Deal Reports). Add filters and transforms between steps when you need them.[1]

Can Faraday trigger actions in Ignition Reporting, and Ignition Reporting 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 Ignition Reporting?

No. Faraday-to-Ignition Reporting 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 Ignition Reporting in real time?

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

You can build your Faraday + Ignition Reporting 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 Ignition Reporting integration.

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

Explore Faraday and Ignition Reporting, or get started