Stripe

OpenContact can import Stripe Customers into a project as contacts.

Connect Stripe

In Stripe, create a restricted API key with read access to Customers, Charges, and Invoices. Do not use a publishable key. The connection form also asks for a webhook signing secret, which Stripe shows after you create the event endpoint. Enter both values in Connections → Stripe; OpenContact encrypts them at rest.

Import customers

After connecting, refresh the available sources and select Stripe customers to import. Customers without an email address are skipped. OpenContact imports the customer’s email, name, phone, country, creation time, delinquency flag, and Stripe customer ID. It also calculates purchase and revenue fields from successful customer charges and paid invoices. Revenue is kept per currency in the smallest unit (for example, stripe_net_revenue_usd_minor).

Useful fields include stripe_has_purchased, stripe_purchase_count, stripe_last_purchase_at, stripe_customer_delinquent, and gross/refunded/net revenue fields. Use numeric gt/lt conditions to build segments such as customers with no purchases or customers whose net USD revenue exceeds a threshold, then send them to any supported provider or internal list.

Automatic customer sync

New customers are polled every five minutes; a daily reconciliation refreshes all customers. Stripe webhook events can refresh payment and customer changes sooner. All resulting contacts flow through OpenContact’s normal contact rules, so create rules scoped to the Stripe source and route them to any supported destination or internal list.

Stripe customer data does not prove that someone opted in to marketing. Imported contacts are therefore marked unknown. They can be used by deliberately configured CRM, transactional, or internal-list workflows, but should not be routed to an email-marketing provider as subscribers until marketing consent is obtained and recorded.

Payment event automations

Stripe can also trigger Pipedrive deals and activities for successful or failed payments, paid or failed invoices, completed Checkout sessions, and supported customer changes. In Stripe, create a webhook endpoint using the OpenContact Stripe callback URL for your connection, select the events used by your rules, and copy its signing secret into the Stripe connection.

Then open Sync Rules → Stripe event automations, select the Stripe source and Pipedrive destination, choose an event and action, and save the rule. Stripe retries are de-duplicated by event ID, and every request must pass Stripe’s signature check before a rule runs.