Start work on the right payment event
The payment model determines the trigger. A one-time purchase, installment and subscription renewal should not all create the same onboarding task.
- Tools
- Stripe, Zapier, ClickUp
- Trigger
- A supported Stripe event confirms the agreed successful payment condition for an included product or service.
- Outcome
- Match the customer and engagement, create or locate the ClickUp onboarding work and record payment-related exceptions for the delivery owner.
Choose the success condition
Identify the relevant Stripe object and success event, then check the current payment state and included products. Creating an invoice or starting checkout is not evidence that payment succeeded. Delayed payment methods require their own confirmed-success path.
Match the engagement
Use Stripe customer and payment references alongside an agreed engagement identifier. Define whether another payment funds existing work, buys another service or starts a new project. Email matching alone cannot resolve every case.
Create work once and keep the reference
Map the service, owner and payment context into ClickUp. Save the source payment and destination task IDs so duplicate events and retries find existing work. A task-write failure should leave a recoverable record of the paid engagement.