Integration design guides
Plan how editors, databases, automation tools and model interfaces can support your work. Explore the data, permissions and checks each connection needs.
Choose a useful reading path
Start with a concept guide if the terminology is new. Move to a workflow article when you have a specific task, then use the relevant workspace surface with a small input you can verify.
Turn an idea into a useful task
Pick one question and one source you know well. Decide what a good result should contain, try the workflow, and inspect its evidence before widening the scope. For comparisons, record the conditions under which each result was measured.
A practical starting point
Connect an external system deliberately. These steps describe the GoCux workflow and its permission boundaries.
- Inspect the integrations actually listed in your workspace. Identify the data source, the account that owns it, and the operation you need before granting access.
- Use the narrowest available permission and keep credentials inside the supported connection flow. An integration article does not mean a connector is installed or authorized.
- Test a read operation with a small, known record. Review its scope and output before allowing a workflow to make an external change.
What to verify
Confirm both authorization and the observed result. A successful sign-in is not evidence that every advertised connector operation works.
Start reading
17 resources
- Integrations
An external AI gateway: integration design guide
Plan a dependable route from an assistant request to a model response. Decide how usage, delays and unavailable services will appear to the person doing the work.
- Integrations
Anthropic: integration design guide
Plan an assistant workflow around Anthropic messages and tools. Decide what context to share, which actions need review and how to check the result.
- Integrations
AWS Marketplace: integration design guide
Plan how a service purchased through AWS Marketplace fits into your work. Identify the account, subscription and information the workflow needs.
- Integrations
Cursor: integration design guide
Bring a development task into focus with Cursor. Choose the repository, define the intended change and review how editor tools use your project context.
- Integrations
ElevenLabs: integration design guide
Plan a voice experience that makes the next action clear. Connect spoken requests to reviewable tasks and decide how confirmations and corrections should work.
- Integrations
Gemini Enterprise: integration design guide
Plan how an enterprise assistant uses organizational knowledge. Start with a document collection and check that people can retrieve only the information intended for them.
- Integrations
Google Cloud Marketplace: integration design guide
Plan how a Google Cloud Marketplace service participates in your workflow. Connect the purchasing account, service scope and intended use before sharing data.
- Integrations
Ollama: integration design guide
Explore a workflow that uses local inference with Ollama. Identify the model context, the tools involved and the information that needs to leave the device.
- Integrations
OpenAI: integration design guide
Plan how OpenAI messages, tool results and streamed answers fit into an application. Start with one request and a clear expectation for the response.
- Integrations
OpenCode: integration design guide
Plan a development workflow with OpenCode. Keep the working directory, project context and permission to change files clear throughout the task.
- Integrations
OpenRouter: integration design guide
Plan how a model-routing service supports your assistant. Consider model availability, response quality and what the user should see when a request cannot finish.
- Integrations
Pi: integration design guide
Explore how a Pi extension can support a focused task. Define its input, expected result and the permissions it needs before expanding its responsibilities.
- Integrations
Snowflake: integration design guide
Plan a research workflow around a small, known warehouse query. Choose the permitted data and decide how its results will support a report or artifact.
- Integrations
Supabase: integration design guide
Plan how application data can support an agent task. Start with a known record, check who can access it and follow the result through the workflow.
- Integrations
Superhuman: integration design guide
Plan an email workflow that keeps context and review together. Decide what to read, what to draft and how recipients and attachments will be checked before sending.
- Integrations
Vercel AI SDK: integration design guide
Plan an assistant interface with Vercel AI SDK. Connect messages, streamed answers and tool results while keeping cancellation and incomplete output understandable.
- Integrations
Zapier: integration design guide
Plan an automation from one clear trigger to a result you can verify. Review each step, identify possible duplicates and decide where an external change needs approval.