PORTAL / GETTING STARTED / Phase 4 — Connect your tools
Phase 4 — Connect your tools
API keys: what to get, where to get each one, and where to put it. Do only the ones your workflows need.
Workflows talk to your real tools through API keys stored in your .env file (local only, never in git). You don't need everything on this page — your install plan (from the Map phase) says exactly which ones your first workflows use. Connect those, skip the rest until needed.
How to add any key
- Open
.envin your repo folder (copy.env.exampleto.envif it doesn't exist). - Paste the key after the
=sign, no quotes, no spaces:META_ACCESS_TOKEN=EAAG... - Save. Done — skills pick it up automatically.
Treat .env like your bank card PIN. We will never ask you to send us keys by email or chat; during the install we work inside your environment, keys stay with you.
Where each key comes from
| Tool | Key(s) | Where to get it | Needed for |
|---|---|---|---|
| Meta Ads | System User token | Business Settings → Users → System users → generate token with ads_read/ads_management | Campaign builds, ad analysis, reporting |
| Google Ads | Developer token + OAuth refresh token | developers.google.com/google-ads — we do this WITH you on a call, it's the fiddliest one | Search-term cleanup, keyword research, reporting |
| Google Workspace | OAuth (guided script in the kit) | We run scripts/google_auth.mjs together once | Docs, Sheets, Drive, Gmail deliverables |
| Your CRM (GoHighLevel) | Location API key | GHL → Settings → API keys | Lead tracking, reporting, booking flows |
| Your CRM (HubSpot/Pipedrive/other) | Private app token | We map your CRM's equivalent during install | Same as above |
| Krea | API key | krea.ai → Settings → API | Image generation for ad creatives |
| ElevenLabs | API key | elevenlabs.io → Profile → API key | Voiceovers for video ads |
| HeyGen | API key | heygen.com → Settings → API | Avatar-less video ads |
| Firecrawl | API key | firecrawl.dev | Web scraping (competitor intel, site audits) |
| Instantly | API key | instantly.ai → Settings → Integrations | Cold email sending |
| MillionVerifier | API key | millionverifier.com | Email verification |
| ClickUp / your PM tool | API token | ClickUp → Apps → API | Task creation from briefs and meetings |
Full directory with pricing notes: Tools & APIs.
Checklist before Phase 5
- The 3-6 keys named in YOUR install plan are in
.env .envis NOT visible on github.com (check your repo — if you can see it there, tell us immediately)- Test each connection by asking Claude: "test the Meta connection" (each connector has a check)