Start with Automation

PATHFIX AUTOMATION

Build the workflow once. Run it for every connected user.

Build API workflows that run in each user's connected account. Chain APIs, transform data and respond to webhooks without building the execution infrastructure yourself.

Start with Automation Explore documentation
View pricing →
Workflow definition
  1. TriggerWebhook from a user's account
  2. APIFetch related data
  3. TransformMap and reshape the response
  4. DeliverSend to your endpoint
  • AUser Aown connectionexecution
  • BUser Bown connectionexecution
  • CUser Cown connectionexecution
Illustration

One workflow. Thousands of user connections.

Your customers connect their own accounts. You define the workflow once. Pathfix executes it in the context of the appropriate connected user, so each customer's data and API activity remain associated with their own connection.

SharedWorkflow definition
AUser A
Google Calendar A
Workflow execution A
BUser B
Google Calendar B
Workflow execution B
CUser C
Google Calendar C
Workflow execution C

Each execution uses that user's authenticated connection. A workflow runs for a user when its configured trigger fires for that user's eligible connection, not for every user at once.

Build complex API workflows without building the engine.

Create workflows by chaining API requests, passing data between steps, applying conditions and transforming responses. Connect supported provider APIs or define custom API calls to build the integration logic your application needs.

Pathfix Automation workflow editor showing a chain of steps with a condition branch and the step properties panel
The Pathfix Automation workflow editor

  • Visual Workflow Builder

    Design and connect workflow steps visually.

  • API Builder

    Configure custom API requests and use available API definitions.

  • Dynamic Data

    Use the output of one API call in subsequent steps.

  • Data Transformation

    Map, process and reshape API response data.

  • Conditions & Loops

    Control workflow execution using branching logic and iteration.

  • Reusable Configuration

    Manage constants, connections and reusable values.

Respond when something changes.

Trigger workflows through supported webhooks, endpoint calls or schedules. For supported OAuth providers, Pathfix can listen for changes in individual connected user accounts and initiate the appropriate automation.

  • User-level Webhooks

    Listen for supported changes in individual users' connected accounts.

  • Multiple Trigger Types

    Start workflows through webhooks, endpoint calls or schedules.

  • Webhook Subscription Management

    Manage and monitor user-level webhook subscriptions, including their connection status.

Pathfix Automation webhook provider selection list
Selecting a webhook provider
Schedule options for an automation endpoint: Manual, every 15, 30 or 45 minutes, every hour, once every day
Schedule options for an endpoint

Run on a schedule

Set an automation's endpoint to run manually, every 15, 30 or 45 minutes, every hour or once a day, with an optional start date and time.

Webhook availability and supported events vary by provider. Listening for changes in end users' accounts works with connections authorized through Pathfix OAuth. The webhooks documentation lists the currently supported providers.

Know what happened at every step.

Inspect workflow executions, track their status and troubleshoot integration behavior using the monitoring capabilities built into Pathfix Automation.

Pathfix Automation Monitor showing a completed run, its steps and the request data it received
Monitor, with sample data

  • Workflow execution tracking

    Follow each run in Monitor.

  • Execution status and history

    Browse completed runs and the request data each one received.

  • Development and Live environments

    Build and test in Dev, then publish to Live. Live automations can be enabled or disabled; changes are made in Dev.

  • Investigating failed executions

    Review a run's data to see where it went wrong.

Connected users. Automated workflows.

Pathfix OAuth and Pathfix Automation are separate products that work together. Pathfix OAuth handles the authorization and token lifecycle for connected users. Pathfix Automation uses the appropriate connections to execute configured API workflows and respond to supported events.

  1. 01

    User connects account

    In your application.

  2. 02

    Pathfix OAuth

    Manages authentication and tokens.

  3. 03

    Pathfix Automation

    Executes the configured workflow.

  4. 04

    Your application

    Receives or uses the result.

Automation can also call custom APIs and use other supported connection configurations, so workflows are not limited to OAuth-connected providers.

Pathfix OAuthAutomation documentation
Pathfix Automation connections list including Pathfix OAuth, Slack, Google Sheets and Facebook
Connections in Pathfix Automation

From a user event to a completed workflow.

A customer connects their Google Calendar account to your SaaS application. When a supported calendar event occurs, a webhook triggers your configured workflow for that user. The workflow retrieves relevant information, processes it and sends the result to your configured endpoint or next API step.

  1. Connect

    The user connects Google Calendar through Pathfix OAuth.

  2. Listen

    A supported calendar event triggers the webhook for that user.

  3. Process

    The workflow fetches and transforms the data it needs.

  4. Deliver

    The result goes to your endpoint or the next API step.

You configure the workflow and decide the business logic. Pathfix does not supply a prebuilt Google Calendar workflow.

Build once. Automate for every connected user.

Move API orchestration, webhook handling and workflow execution out of your application code and into Pathfix Automation.

Start with Automation Read the documentation
Automation pricing