Back to apps
Payments and accountingNext connector

Stripe × Volimox

Connect approved payment events to customer records, receipts, and operational follow-up.

Best for online deposits, payment links, and card-based service workflows.

Connection boundary

Volimox only takes the permissions this workflow needs. The account owner reviews access before anything is activated.

Request a pilot
01

Special workflows for Stripe.

Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.

Use case 01Stripe × Volimox

Approved quote to payment link

Ask for payment only after the quote and customer details are ready.

Starts when

A Volimox quote reaches an approved payment state.

Result

The customer receives one traceable payment request tied to the job.

Volimox workflow

  1. 01Volimox verifies the customer, amount, service, and quote reference.
  2. 02Volimox creates a Stripe customer or payment link with an idempotent operation key.
  3. 03The operator reviews the link before it is sent through the chosen channel.

Human checkpoint

No payment request is created from an unapproved quote or ambiguous customer.

Use case 02Stripe × Volimox

Payment succeeded to booking update

Connect a verified Stripe payment to the operational record and customer follow-up.

Starts when

Stripe reports a successful payment or paid invoice for a linked customer.

Result

Payment status becomes a reliable input to the customer handoff.

Volimox workflow

  1. 01Volimox reconciles the provider event to the matching quote or booking.
  2. 02Volimox updates the workflow state and records the provider payment reference.
  3. 03The operator approves the confirmation or lets the next scheduling step begin.

Human checkpoint

Provider identity and amount are checked before a booking is marked paid.

02

Supported triggers and actions.

A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.

Triggers

  • Payment succeeded
  • Checkout completed
  • Refund created
  • Invoice paid

Actions

  • Create payment link
  • Create customer
  • Create invoice
  • Read payment status
03

Detailed connection code.

This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.

TypeScript · server only

Create a deposit checkout session

Copy-ready reference
import { createZapierSdk } from "@zapier/zapier-sdk"

const zapier = createZapierSdk({
  apiKey: process.env.ZAPIER_API_KEY,
})

export async function runStripeAction() {
  const { data: connection } = await zapier.findFirstConnection({
    app: "stripe",
    owner: "me",
  })

  if (!connection) {
    throw new Error("No approved Stripe connection was found")
  }

  const result = await zapier.runAction({
    app: "stripe",
    action: "create_checkout_session",
    connection: connection.id,
    input:
    {
      "mode": "payment",
      "priceId": "{{env.STRIPE_DEPOSIT_PRICE_ID}}",
      "quantity": 1,
      "customerEmail": "{{lead.email}}",
      "successUrl": "https://volimox.com/payment/success?lead={{lead.id}}",
      "cancelUrl": "https://volimox.com/payment/cancel",
      "metadata": "volimox_lead_id={{lead.id}}"
    },
  })

  return result.data
}
Action identifiers and available fields can vary by provider account, connector version, and plan. Validate the selected action in a sandbox connection before production activation.
04

Connection setup.

The setup path is specific to the provider. We will never ask you to paste credentials into a public page.

Stripe OAuth

A reviewable connection, step by step.

  1. 01Stripe account owner approval
  2. 02Select connected account
  3. 03Review payment and customer scopes
Next connector

This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.

Tokens and provider credentials belong in the authenticated connection console, never in this public page.
Request a pilot

Related apps

Common handoffs with Stripe.

Provider names and logos belong to their respective owners. Volimox only uses them to describe connection possibilities and configured workflows.