Command Palette

Search for a command to run...

Skip to content

Build your first workflow.

Use the visual workflow builder to automate payment events. Send notifications, update systems, and trigger actions when payments succeed or fail.

Writtenintermediate10 min

Overview

Reevit's workflow engine lets you build visual automations that react to payment events. When a payment succeeds, fails, or gets refunded, your workflow can send emails, call webhooks, update databases, add delays, or branch based on conditions, all without writing code.

Key concepts

  • Trigger: The event that starts the workflow (e.g., payment.succeeded)
  • Action: Something the workflow does (e.g., send an email, call a webhook)
  • Condition: A branching point that checks a value (e.g., amount > 1000)
  • Delay: Pause the workflow for a set duration before continuing

Create a workflow

  1. Navigate to Workflows

    From your dashboard sidebar, click Workflows. You'll see existing workflows and a Create Workflow button.

  2. Name your workflow

    Click Create Workflow. Give it a descriptive name like "Send receipt on payment success" and an optional description.

  3. Set the trigger

    Every workflow starts with a trigger. Choose from available events:

    • payment.succeeded: A payment was completed
    • payment.failed: A payment attempt failed
    • payment.refunded: A refund was processed
    • subscription.created: A new subscription started
    • subscription.canceled: A subscription was canceled

    Drag the trigger node onto the canvas.

  4. Add actions

    Connect action nodes to your trigger:

    Send Webhook: POST event data to any URL

    Examplejson
    {  "url": "https://your-api.com/webhooks/reevit",  "headers": {    "X-Custom-Header": "value"  }}

    Send Email: Send a templated email to the customer or your team

    HTTP Request: Make any HTTP call to external services

    Delay: Wait before executing the next step (e.g., wait 1 hour, then send a follow-up)

  5. Add conditions (optional)

    Use condition nodes to branch your workflow:

    • If amount > 50000 → Send Slack alert to finance team
    • Else → Just log the payment

    Conditions can check any field from the trigger event data: amount, currency, customer email, provider, metadata, and more.

  6. Activate the workflow

    Click Activate in the top right. The workflow will start processing events immediately. You can deactivate it at any time without deleting the configuration.

Example: Payment success receipt

Here's a simple workflow that sends a receipt when a payment succeeds:

  1. Trigger: payment.succeeded
  2. Condition: Check if customer_email exists
  3. Action: Send receipt email to customer
  4. Action: POST to your backend to update order status

Testing workflows. Use sandbox mode to trigger test events. Every sandbox payment fires the same events as live payments, so your workflows get tested end-to-end.

Workflow execution history

Every workflow run is logged with:

  • Status: Success, failed, or skipped
  • Duration: How long the workflow took
  • Step details: Input/output for each node
  • Error info: Clear error messages if something fails

Navigate to a workflow and click History to see all past executions.

Next steps

Stop losing payments to provider downtime.

Free for your first 1,000 payments a month, and failed payments are never billed. Connect a provider and take your first payment before the coffee gets cold.