Authenticate calls to the Snapshots API using your API key with the saas/location.read scope.
Authenticate the Stripe (Legacy) connection with your Stripe API keys and secure tokens, then authorize data transfers to Snapshots.
GET /locations (example); GET /customers; GET /invoices; other endpoints available in the integration.
Trigger: a location change in Stripe updates the corresponding location in Snapshots.
Actions: create or update a Snapshots location when Stripe location data changes.
GET /locations
id, name, address, country, currency
Trigger: a new Stripe customer creates or updates a Snapshots contact.
Actions: map customer fields to Snapshots contact fields; create or update contact.
GET /customers
id, email, name, metadata
Trigger: a Stripe invoice is created or paid to reflect status in Snapshots.
Actions: log invoice details and update payment status in Snapshots.
GET /invoices
id, amount_due, currency, status, customer_id
Automate data flow without writing code.
Reduce manual data entry and human error.
Faster onboarding for new Stripe accounts.
Overview of data flow, triggers, actions, and endpoints in the Stripe (Legacy) to Snapshots integration.
Application Programming Interface — a set of rules that enables software components to communicate.
A real-time notification mechanism that informs one app when a specified event occurs.
A secure authorization framework that allows apps to access data without sharing credentials.
A URL path through which an API can be accessed to perform actions.
Automatically update payment status in Snapshots when Stripe events fire.
Hook location changes in Stripe to update or create related records in Snapshots.
Trigger marketing and lifecycle workflows in Snapshots based on Stripe events.
Obtain your Stripe API keys and your Snapshots API key, then authorize the connection.
Set up Stripe webhooks to notify Snapshots of events like locations, customers, and invoices.
Define mapping between Stripe fields and Snapshots fields, then run a test flow.
The Snapshots API provides a standard way to access and manipulate your data from Stripe (Legacy) without changes to your existing apps. You will authenticate with your API key and request only the saas/location.read scope as needed. This ensures you can securely pull location and related data. When you test, start with the GET /locations endpoint to verify connectivity and data mapping.
No-code setup is possible for most connections using the webhook-based approach and prebuilt field mappings. You can configure the integration in the Snapshots app UI, connect your Stripe account, and map key fields without writing code. If you need custom logic, consider using optional filters and mapping rules.
The core endpoints you may see in this integration include locations, customers, and invoices. Depending on your use case, you may also leverage additional endpoints exposed by the Stripe API and mapped in Snapshots. The docs in the integration will guide you through the exact available endpoints.
Testing involves sending a test event from Stripe to Snapshots or triggering a manual test in the Snapshots UI. Verify that locations, customers, and invoices map correctly and that status updates flow through your automations. Use sample data to validate field mappings and triggers.
Security best practices include using OAuth where available, rotating API keys regularly, and limiting scope to what is required. Store keys securely, use encrypted channels, and monitor for unusual activity using Stripe and Snapshots audit logs.
Yes. You can extend mappings to additional Stripe fields by adding rules and mappings in the Snapshots UI. The no-code approach supports many field types, including custom metadata and nested objects.
API endpoints for this integration are typically documented in the Snapshots app under the Stripe (Legacy) connector. You will find a list of endpoints like locations, customers, and invoices, plus any additional endpoints you enable in your workspace.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
