Common third-party services are ready to wire in by name — mention the provider and the use case, and the generator adds the SDK, environment variables, and a typed wrapper into your repo.
Payments
- Stripe — Checkout, Subscriptions, Connect.
- Tap — KSA-friendly card processing.
- Paylink — invoice + redirect flow.
Messaging
- SendGrid — transactional and marketing email.
- Twilio / WhatsApp Business — SMS and WhatsApp.
Storage and media
- S3 / MinIO — uploads with presigned URLs.
- Cloudinary — image transforms and delivery.
How to add one
- Name the provider with the outcome you want — "send an SMS via Twilio when an order ships".
- The generator wires the SDK and adds the env keys to
.env.example. - It calls the service from the right place in your app (e.g. after the order status flips).
- You fill the real credentials in
.envand test in preview.
Common mistakes to avoid
- Wiring a provider without a use case. Say when it should fire, not just "add Twilio".
- Committing keys. Real values live in
.env, never in the repo. - Skipping the test. Trigger the action in preview once to confirm the integration before you rely on it.
FAQ
My provider isn't listed — can I still use it?
Usually yes. If it has a REST API or an npm SDK, ask the AI to integrate it and give it a docs link.
Can I use more than one at once?
Yes — e.g. Stripe for payments and SendGrid for email in the same app. Each gets its own file and env keys.
Which payment provider should I pick?
Stripe for global cards; Tap or Paylink for KSA-focused flows. You can switch later by prompt.