Opening your saved workspace. Public pages remain available below.

← All starter kits & goal guides
FRONTIERS / PRACTICAL GOAL GUIDE

Connect your tools. Keep control.

Bring the right systems into one workflow with clear permissions, ownership, and testable data flows.

Your roadmap0 of 15 checks marked · opening your workspace

STEP 1 OF 5

Map the connection

Define what should move between systems before authorizing access.

Your next actions

Resources for this step

Choose what fits. Alternative platforms are choices, not extra requirements. Use your own authorized accounts.

Planning toolFigJam ↗

Map a process, journey, or customer hypothesis on a shared whiteboard.

Cost
Free and paid plans; limits vary
Setup
Account; browser
Tracking toolGoogle Sheets ↗

Maintain a simple experiment log, data dictionary, cost model, or operations report.

Cost
Personal and paid workspace options
Setup
Account; use controlled sharing
WHAT YOU SHOULD HAVE

A field map and a clear integration boundary.

TAKE THE BRIEF INTO YOUR ASSISTANT

Start with a better brief.

Fill in the brackets for your selected approach: Connect two apps.

Read the starter prompt

Help me connect [source app] to [destination] for [purpose]. Identify available native integrations first, then a supported connector. Document data direction, fields, scopes, source of truth, and revocation. Start read-only with sample data, then test access boundaries and failures. Do not expose credentials in prompts or source code. Start with the smallest useful version and keep additional services optional. Recommend only relevant tools and verify supported skills or plugins before using them. Explain costs and permissions. Record checks actually performed and unresolved issues. Ask for approval before publishing, sending messages, connecting live accounts, or spending money.

Checks record your progress; they do not execute tools or verify business results. Official resources reviewed November 2026. Check current pricing, license terms, and host compatibility. These guides have not been tested as end-to-end business or integration workflows.

Browse related repositories →
WORK ON YOUR OWN EXAMPLE

Check integration feasibility

Complete this for one proposed connection. Confirm access before promising a feature or building around it.

Open the integration feasibility worksheet

Loading saved notes… Do not enter credentials or confidential client data. Status: opening your workspace.

Which systems and direction?

List source, destination, account owners, direction of sync, and the source of truth.

Does supported access exist?

Link official API/native integration docs. Record what you verified and the date; do not assume a screen feature has an API.

Is access gated?

Record required account plan, partner approval, region, sandbox availability, and lead time.

What permissions and data are needed?

Document minimum scopes, authorized data, credential owner, revocation, and retention needs. Do not enter actual keys or tokens.

What does it cost and what are the limits?

Record plan costs, per-call/task usage, rate limits, quotas, and expected load. Link current sources.

How do records map?

Define identifiers, field mapping, duplicate handling, sync conflicts, and event ordering.

What happens when it fails?

Plan retries, idempotency, alerts, manual fallback, replay safety, and the owner of failures.

What will prove the connection works?

Specify sandbox fixtures, a read test, an approved write test, denied-access cases, acceptance criteria, and unresolved blockers.

0 blocked · 8 items need assessment or follow-up. These are your own labels, not an automated verdict.

A completed worksheet is a feasibility record, not a working integration or a security certification. Exports are created locally; this worksheet does not send notes to an AI or external service.

GO DEEPER

More learning resources.

Expand a topic for courses, documentation, and tools from the supplied learning curriculum. Links already recommended in the guide above are omitted.

Understand APIs and test requests by hand3 resources

An API call is just an HTTP request. If you can send one by hand and read the reply, connecting tools stops being magic.

docsMDN: Overview of HTTPDetails +

Requests, responses and status codes explained by the browser makers.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
toolBrunoDetails +

Open-source, local-first API client that stores collections as plain files you can commit to Git.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
toolWebhook.siteDetails +

See exactly what another system sends your way.

Cost / access
free tier
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
Learn tokens versus OAuth4 resources

Some tools give you a private token for your own account; apps that act for many users use OAuth. Pick the narrowest one that works.

docsOAuth 2.0 overview (oauth.net)Details +

The industry-standard authorization protocol and its flows for web, mobile and device apps.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsOAuth.com: OAuth 2.0 SimplifiedDetails +

A practical guide with step-by-step flows and real examples.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsHighLevel Private Integrations guideDetails +

Real-world example of a scoped private token you can create, rotate and delete, instead of a full-access key.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsHighLevel API documentationDetails +

REST docs for contacts, messaging, calendars, payments and webhooks in a hosted CRM.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
Learn what MCP is and use existing servers4 resources

MCP is an open standard that lets an AI app call your tools and read your data. Use trusted existing servers before writing your own.

docsWhat is the Model Context Protocol?Details +

The official introduction: servers expose tools, resources and prompts that AI apps can use.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsConnect Claude Code to tools via MCPDetails +

How to add, scope and manage MCP servers in Claude Code.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
repomodelcontextprotocol/serversDetails +

Reference server implementations for learning, with pointers to community servers.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
siteOfficial MCP RegistryDetails +

Searchable directory of MCP servers.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
Build or expose your own connector3 resources

When no server exists for your tool, a small MCP server (or an n8n workflow exposed as one) is the cleanest way to give an agent exactly the actions you choose.

docsMCP: Build an MCP serverDetails +

A tutorial that builds a small weather server in Python or other languages and connects it to a client.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsBuild an MCP server for Claude (connectors)Details +

Where to host it, how users authenticate, size and timeout limits, and how to share it.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsn8n MCP Server TriggerDetails +

Lets n8n act as an MCP server so clients can use its tools and workflows.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
Know the MCP risks2 resources

Every connector is a door. Learn the known attacks and scope each one to the smallest set of actions.

docsMCP Security Best PracticesDetails +

Confused deputy, token passthrough, SSRF, local server compromise and scope minimization, each with fixes.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsClaude Code security (MCP section)Details +

Says to write your own servers or use providers you trust, and notes Anthropic does not security-audit MCP servers.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
Shortlist an open-source CRM4 resources

Pick two or three to try. Check the licence, since all three below are reported to be AGPL; hosting it for others can bring obligations.

repoTwenty (GitHub)Details +

Modern open-source CRM described as an open alternative to Salesforce, designed for AI; confirm its licence terms in the repo.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
siteEspoCRMDetails +

Long-established open-source web CRM for people, companies and opportunities.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
siteSuiteCRMDetails +

Open-source CRM that keeps data under your control; large user base.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
repoFrappe CRM (GitHub)Details +

Fully featured open-source CRM from the Frappe team, licensed AGPL-3.0.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
Test before you commit4 resources

Choose by a short test: can you import contacts, call its API, receive a webhook, and back it up? Read each product's own docs for those four.

docsTwenty docsDetails +

Product intro and developer guides.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsEspoCRM documentationDetails +

Setup, administration and developer docs, including extensions.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsSuiteCRM documentationDetails +

Install, admin and developer guides for SuiteCRM 7 and 8.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.
docsFrappe CRM: Your first stepsDetails +

Beginner guide: leads, team, email, follow-ups and converting leads to deals.

Cost / access
free · Service usage, hosting, or model access may be separate.
Setup
Follow the linked provider’s current instructions; check account and runtime requirements.

Additional curriculum comes from the supplied AI Frontiers playbooks. Resource descriptions and cost labels are source guidance, not a fresh verification of pricing, compatibility, or results. Open the official instructions before using a tool. Checklist marks are your own progress notes.