Skip to main content

Integration overview

Cocoding AI apps can include integration requirements in the prompt and in follow-up requests. Use this section to plan connector work for services such as Notion, WhatsApp, Telegram, Stripe, Slack, OpenAI, HubSpot, Airtable, and Supabase.

Cocoding AI app marketplace with examples for product planning
Review examples and integration patterns before adding external services to a generated app.

Integration guides​

Notion

Connect pages and databases for tasks, notes, content workflows, and lightweight operations.

Open Notion guide

WhatsApp

Send customer reminders, confirmations, and operational notifications through an approved provider.

Open WhatsApp guide

Telegram

Create bot commands and alerts for lightweight team or customer messaging.

Open Telegram guide

Stripe

Add checkout, subscriptions, payment status, and webhook-backed billing flows.

Open Stripe guide

Slack

Notify internal channels, route events, and add approval or team workflow alerts.

Open Slack guide

OpenAI

Add chat, summarization, extraction, classification, and AI-assisted product flows.

Open OpenAI guide

HubSpot

Sync contacts, companies, deals, and CRM activity with generated apps.

Open HubSpot guide

Airtable

Build apps around existing bases, views, tables, and operational records.

Open Airtable guide

Supabase

Use Supabase for PostgreSQL, authentication, storage, realtime features, and APIs.

Open Supabase guide

How to plan an integration​

  1. Name the external service.
  2. Describe the user workflow.
  3. Identify what data should move in or out.
  4. Confirm whether authentication, OAuth, webhook, API key, or database credentials are required.
  5. Ask Cocoding AI to scaffold a safe configuration pattern.

Integration planning worksheet​

QuestionExample answer
Who triggers the integration?Customer submits checkout, admin approves a record, or scheduled job runs every morning.
What data leaves the app?Email, order ID, message body, invoice amount, file text, or CRM contact fields.
What data returns?Payment status, provider message ID, synced contact, AI answer, or webhook event.
Where should the user see status?Admin table, activity log, billing page, notification center, or project dashboard.
What happens if the provider fails?Retry, mark failed, show setup warning, or let the core workflow continue.
  1. Build the app workflow without the provider.
  2. Add environment variable names and setup warnings.
  3. Add a test-mode provider connection.
  4. Store provider status fields in the database.
  5. Add webhooks or background sync.
  6. Test success, failure, retry, and missing-configuration states.

Prompt example​

Add Stripe checkout for the Pro plan.
Use a backend endpoint for checkout session creation.
Do not hardcode secret keys.
Show a billing status page after payment.

Secret handling​

Do not paste production API keys into normal docs, screenshots, or source files. Store integration secrets in the approved runtime configuration for your deployment.

Good integration prompts​

Ask for secure boundaries in the same prompt as the feature. A useful integration prompt says what the user should see, what the provider should do, where credentials live, and how errors should appear.

Add a Slack notification when a booking is created.
Use server-side environment variables for Slack credentials.
Show delivery status in the admin activity log.
If Slack is not configured, keep the booking flow working and show a setup warning.