Back to apps
Payments and accountingPlanned

Square × Volimox

Connect in-person and online payment events to customer and service workflows.

Best for operators already taking payments through Square.

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 Square.

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 01Square × Volimox

Service request to Square payment link

Create a reviewable Square payment request from an approved service record.

Starts when

A Volimox quote or job is approved for payment collection.

Result

Square payment collection stays connected to the service request.

Volimox workflow

  1. 01Volimox checks the customer and total against the approved job.
  2. 02Volimox creates the customer or payment link in Square.
  3. 03The operator reviews the request and sends it through the configured channel.

Human checkpoint

The amount and customer identity must match the approved job before creation.

Use case 02Square × Volimox

Payment completed to operations update

Move a verified Square payment into the next booking or dispatch state.

Starts when

Square reports a completed payment for a linked customer.

Result

Operations can see which jobs are paid without checking another dashboard.

Volimox workflow

  1. 01Volimox matches the payment to the job using the provider reference.
  2. 02Volimox records the paid state and preserves the payment identity.
  3. 03The operator confirms the next service step or sends a receipt update.

Human checkpoint

Unmatched or duplicate payment events are held for reconciliation.

02

Supported triggers and actions.

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

Triggers

  • Payment completed
  • Refund created
  • Customer created

Actions

  • Create payment link
  • Create customer
  • 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 Square payment link

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

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

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

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

  const result = await zapier.runAction({
    app: "square",
    action: "create_payment_link",
    connection: connection.id,
    input:
    {
      "locationId": "{{env.SQUARE_LOCATION_ID}}",
      "amount": "{{lead.depositMinorUnits}}",
      "currency": "USD",
      "description": "Deposit for {{lead.service}}",
      "customerEmail": "{{lead.email}}"
    },
  })

  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.

Square OAuth

A reviewable connection, step by step.

  1. 01Choose Square location
  2. 02Select payments and customer scopes
  3. 03Verify webhook endpoint
Planned

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 Square.

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