Skip to content
Space Invoices Documentation

Zapier

Use Zapier when you want Space Invoices to sit inside an existing workflow toolchain without writing backend glue first.

This is the right fit for:

  • CRM to estimate handoffs
  • approved form submissions that should create draft invoices
  • simple internal ops workflows that should create and send documents
  • teams that want a fast proof of value before building a deeper API integration

Available Actions

The current Zapier app supports these actions:

  • Create Invoice
  • Create Estimate
  • Create Invoice and Send
  • Create Estimate and Send
  • Send Document Email

The create and send actions use multiple Space Invoices API calls under the hood. Zapier creates the document first, then sends it with the email endpoint.

Authentication

Zapier uses the same authentication model as the API:

  • api_key
  • entity_id
  • optional api_base

The connection test validates the selected entity with the existing API credentials.

Common Field Mappings

Most workflows map a small set of fields into Space Invoices:

  • customer name
  • customer email
  • document date
  • due date or valid-until date
  • one or more line items
  • item quantity
  • item price
  • optional note, reference, and metadata

The current Zapier app is optimized for straightforward document creation flows. Use the JavaScript SDK or direct API when you need richer custom logic, larger payload shaping, or tighter product-native control.

Current Constraints

  • Email sending is a separate endpoint, even when exposed as a single Zapier action.
  • Customer and document IDs are currently best entered from known values or prior Zap steps.
  • Zapier is best for lighter workflow automation, not embedded invoicing UI.
  • The Zapier app should be treated as an automation layer on top of the same API model, not a separate product surface.

CRM to estimate

When a deal reaches proposal stage:

  1. Trigger from the CRM
  2. Create an estimate in Space Invoices
  3. Optionally send the estimate immediately

Approved form to invoice

When an internal form or order approval is completed:

  1. Trigger from the form tool
  2. Create an invoice in Space Invoices
  3. Send the document by email in the same Zap

Ops handoff to draft invoice

When finance or operations wants a review step:

  1. Trigger from the upstream system
  2. Create the invoice as a draft
  3. Final review happens inside Space Invoices before live sending

When To Use Another Path Instead

Choose another integration path when:

  • you need embedded invoicing screens in your product
  • your backend needs full control over document orchestration
  • you want typed SDK workflows and direct API ownership
  • you need more complex tenant-aware product logic

See Choose Your Path if you are still deciding.