SalesAutopilot integration
Prerequisites, setup, field mapping, testing, and troubleshooting for the SalesAutopilot connection.
Use the SalesAutopilot integration to upsert the subscriber and loyalty fields.
stmpr sends the selected data to the provider.
Connecting the account does not activate a workflow by itself. Select the loyalty card, trigger, destination action, and customer matching rule separately.
SalesAutopilot
Image placeholder: SalesAutopilot: create the required access
https://stmpr.io/dashboard/integrations
Why use this?
Replace manual data transfers with a verified and observable workflow.
Idempotency prevents duplicate rewards, while consent gates protect marketing data transfers.
- 1A consented customer or loyalty milestone
- 2Authentication, duplicate protection, and customer matching
- 3Upsert the subscriber and loyalty fields
Step by step
- Prepare SalesAutopilot API access and the target list identifier.
- Create the required API, OAuth, or webhook access in SalesAutopilot with the narrowest practical permissions.
- In stmpr, open API & Webhooks and create an API key or a webhook. SalesAutopilot has no Connect action, so the link runs through Zapier, Make or your own integration, and it needs a plan that includes API access.
- In Zapier or Make, build the scenario: the trigger fires at the provider, and the destination action calls the stmpr API.
- Configure customer matching in the scenario. Prefer email or phone; use a provider ID only as a stable secondary key.
- Run a test with a test customer, then deliver the same event again. Pass a stable event ID, or duplicate protection has nothing to work with.
- Test failed delivery, revoked access, a missing customer, cancellation or refund, and consent withdrawal.
- After activation, check the first live events in the delivery log. To disconnect, disable the scenario before revoking the API key.
What you select and verify
- Trigger: a consented customer or loyalty milestone
- Action: upsert the subscriber and loyalty fields
- Loyalty card, business, or location
- Customer matching and required fields
- Consent, refund, cancellation, and no-show rules
- Test data, duplicate protection, and delivery log