Automate order-to-cash
Create SalesDocument, reserve inventory and generate invoices automatically.

Build in-app integrations that create and sync Customers, Sales Documents, inventory levels and shipping actions. Automate order-to-cash workflows, batch updates and inventory reconciliation, then publish those integrations inside your SaaS product.
Create SalesDocument, reserve inventory and generate invoices automatically.
Keep Customers and pricing consistent between systems.
Run bulk updates using SalesPad batch and sequentialBatch endpoints.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Integrate your app with SalesPad to create and sync Customers, SalesDocument (orders/invoices), and Inventory records and automate order-to-cash workflows. SalesPad exposes a customer-hosted Web API supporting CRUD, OData query options and batch endpoints. Review the SalesPad Web API documentation for endpoints and request examples. (portal.salespad.net)
PRODUCT USE CASES
Quickly create integrations that sync Customers, push Sales Documents, update Inventory and run batch updates. Publish those automations in your embedded marketplace for each customer account.
Create SalesDocument records in SalesPad when an order is placed, then trigger inventory reservation and invoicing.
Sync Customer records and pricing updates between your app and SalesPad to keep accounts aligned.
Read Inventory records with OData queries and push bulk updates via batch endpoints to reconcile stock levels.
ORCHESTRATION
Cyclr sits between your SaaS product and SalesPad to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
SalesPad processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore SalesPad methods you can orchestrate through Cyclr.
Get a customers address record.
Get Customer Address Codes.
Finds Addresses matching the supplied Zip Code.
Creates a customer address. Add custom fields in the following format: userfields.fieldname - for example userfields.XDealerCode
Update a customer address. Add custom fields in the following format: userfields.fieldname - for example userfields.XDealerCode
Search address records using OData filtering.
Search customer records using OData filtering.
Get a list of customer records with match by name.
Create a customer with address in Salespad.
Create a customer in Salespad.
Returns a list of customers that have been modified since last run.
Get Customer By Customer Number.
Get a list of customer records.
Create a new unique Customer Number for a new Customer based on their name.
Update a SalesPad customer.
Creates an item record.
Get an item record.
Updates an item record.
Copy existing Item to new Item and update from ItemMaster body before saving.
Get item records.
Creates a sales document payment record.
Creates a sales line item record.
Updates a sales document record.
Get the requested sales documents.
Creates a sales document record.
List sales documents.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing SalesPad integrations in Cyclr.
Customer-hosted SalesPad WebAPI (instance-specific base URL)SalesPad username and password for Basic auth; SalesPad WebAPI base URL; Cyclr may persist Session-ID.
CRUD (Customer, SalesDocument, Inventory); OData queries; Batch/sequentialBatch; Session management.
Most GET endpoints support OData query options ($filter, $orderby, $top, $skip). Batch and sequentialBatch endpoints exist for grouped requests. (portal.salespad.net)
Refer to the vendor API documentation for current limits.
IMPLEMENTATION
SalesPad Web API uses Basic authentication to obtain a Session GUID; include the Session-ID header for subsequent requests. Confirm which options the Cyclr connector exposes in Console. (portal.salespad.net)
SalesPad username and password for Basic auth; SalesPad WebAPI base URL; Cyclr may persist Session-ID.
SalesPad WebAPI is typically self-hosted; run Database Update and ensure API licensing first. (portal.salespad.net)
COMMON QUESTIONS
It can create and sync Customers, SalesDocument (orders and invoices) and Inventory records, and run batch updates to automate order-to-cash workflows. SalesPad Web API exposes CRUD endpoints, OData query options and batch endpoints. (portal.salespad.net)
SalesPad uses Basic authentication to obtain a Session GUID; include that Session-ID header on subsequent requests. Confirm which credential fields Cyclr exposes when installing the connector. (portal.salespad.net)
Yes. Use Cyclr to build multi-tenant workflows and publish them in your embedded marketplace; each customer points to their SalesPad WebAPI instance and credentials. Cyclr handles orchestration and reuse while you govern access.
Yes. You can expose SalesPad actions (for example create SalesDocument, update Inventory) as governed MCP tools so product and support teams can use them under access policies.
KEEP EXPLORING
Related ERP connector for customer-facing integration workflows.
Related connectorRelated Billing/Payment connector for customer-facing integration workflows.
Related connectorRelated Billing/Payment connector for customer-facing integration workflows.