Connectors
This page lists common connector planning notes. It does not replace each provider's official configuration guide.
| Connector | Prepare before implementation |
|---|---|
| Stripe | Products, prices, checkout flow, webhook events, test mode keys. |
| Slack | Workspace app, bot scopes, event subscriptions, redirect URL. |
| Business account, phone number, templates, webhook endpoint. | |
| Telegram | Bot token, command list, webhook or polling preference. |
| Notion | Integration token, target database or pages, field mapping. |
| OpenAI | Model use case, budget, prompt boundaries, server-side key storage. |
| HubSpot | App scopes, contact or deal fields, sync direction. |
| Airtable | Base, table, fields, API token, rate limits. |
| Supabase | Project URL, service role boundaries, database schema, auth needs. |
Ask for a safe integration
Add a Slack notification when a booking is created.
Use a server-side webhook URL from environment configuration.
Do not expose the webhook URL in client code.
Connector implementation checklist
- Start with the user workflow before naming the API.
- Use provider test mode or sandbox accounts while building.
- Put all credentials in runtime configuration.
- Ask Cocoding AI to keep provider calls on the server when secrets are involved.
- Add visible setup errors when a required variable is missing.
- Add delivery, sync, or payment status fields so users know what happened.
- Test failure states, not only the success path.