How It Works
Zapier connects SalesBinder with thousands of other apps, helping you automate everyday tasks without writing code. Send SalesBinder activity to your other services, or use activity in another app to create and update records in SalesBinder.
The new SalesBinder v3 integration includes instant triggers, searches, and actions, with secure sign-in using your SalesBinder account. No API key is required.
Join the Public Beta
The new integration is available as a public beta, open to everyone. Accept the invitation below to add SalesBinder v3 to your Zapier account:
Join the SalesBinder v3 Zapier Beta
What Can I Do With This Integration?
You can build automations around customers, prospects, suppliers, contacts, inventory items, invoices, estimates, purchase orders, and sales orders.
For example, you could:
- Send an email or Slack notification when a new invoice is created.
- Add a contact to SalesBinder when someone submits an online form.
- Update another app when customer details change.
- Notify your team when inventory reaches its low-stock threshold.
- Start a follow-up workflow when an invoice is paid in full.
Available Triggers
Triggers start a Zap when something happens in SalesBinder. The integration supports New and Updated events for all nine record types listed above, plus:
- Invoice Payment Received
- Invoice Paid in Full
- Low Stock
These are instant triggers: SalesBinder sends the event to Zapier when it occurs, rather than waiting for Zapier to check periodically. Completion time depends on Zapier and the other apps in your workflow.
Available Searches and Actions
You can find, create, and update each of the supported record types. Searches let you locate an existing record by its ID or an exact matching field before continuing your workflow.
Additional actions include:
- Record Invoice Payment: Record a payment received elsewhere against an invoice. This action does not charge a credit card.
- Adjust Inventory Quantity: Increase or decrease stock, including quantities for a specific variation and location.
Supported actions also include document line items and custom fields.
Connecting Your Account
- Accept the beta invitation above and sign in to Zapier.
- Create a Zap and choose SalesBinder 3 as a trigger, search, or action.
- Connect your account by signing in as a SalesBinder account administrator.
- Review the requested permissions and approve access.
- Choose your event, map the required fields, and test each step.
- Publish your Zap to turn it on.
Your connection appears automatically in SalesBinder’s Integrations area. Zaps that use a SalesBinder trigger also appear under Trigger Subscriptions.
What Is a Zap?
A Zap is an automated workflow connecting two or more apps. It starts with a trigger, such as a new invoice in SalesBinder, followed by one or more actions, such as sending an email or creating a record in another service.
Mapping Record IDs and Operation Keys
When using a SalesBinder trigger to update or find the same record in a later step, map its resource_id to the record ID field. The trigger’s id identifies the event itself.
Actions that create records, record payments, or adjust stock require an Operation Key. Use a unique ID from the source event, with a suffix identifying the action—for example, order-123-create-invoice. Keep the same key when retrying that operation, and use a different key for each new operation. This helps prevent duplicate records, payments, or stock adjustments.
Managing Your Connection
Open your Zapier connection in SalesBinder’s Integrations area to view recent activity, trigger subscriptions, and Delivery Logs.
Turn individual Zaps on or off in Zapier. Multiple Zaps can respond to the same SalesBinder event.
You can also Pause Connection in SalesBinder to pause Zapier access and event delivery for the entire connection. Resume it when you are ready to continue.
Disconnecting revokes Zapier’s access and removes its trigger subscriptions. To use the integration again, reconnect your account in Zapier and re-enable your Zaps.
Troubleshooting
Use SalesBinder’s Delivery Logs to investigate events sent to Zapier. Temporary delivery failures are retried automatically, and failed deliveries can be reviewed and retried where available.
Use Zap History in Zapier to investigate the rest of your workflow, including actions performed in other apps.
Moving From the Previous Integration
Existing Zaps are not automatically migrated to SalesBinder v3. Build new Zaps using the new integration and authorize your account again.