Integration account setup¶
Start with test and production environments. It explains the launcher, secure key prompts, file locations, offline fixtures, and promotion. Then follow your provider's complete account guide. These instructions target ZeoCore 0.11.0 or newer. Earlier wheels do not include this complete surface.
| Integration ID | Get credentials and configure accounts | Test track |
|---|---|---|
hubspot.marketing |
HubSpot | Developer test account; restricted recipients |
kit.marketing |
Kit | Dedicated creator account and designated subscribers |
github |
GitHub | Separate token limited to a disposable repository |
google.mail |
Gmail | Dedicated Google user and seeded mailbox |
google.drive |
Drive | Dedicated user and test folder/files |
google.calendar |
Calendar | Dedicated user and secondary calendar |
google.docs |
Docs | Dedicated user and disposable document |
google.sheets |
Sheets | Dedicated user and disposable spreadsheet |
google.slides |
Slides | Dedicated user and disposable presentation |
notion |
Notion | Test workspace or separately shared test parent |
supabase |
Supabase | Local stack or separate hosted project |
social.bluesky |
Bluesky | Dedicated account; posts remain public |
llms |
OpenAI, Anthropic, Ollama and mock | Separate provider project/workspace or local model; explicit fixture |
pandoc |
Pandoc | Local sample documents and separate output directory |
ffmpeg |
FFmpeg | Local synthetic media and separate output directory |
jupytext |
Jupytext | Local sample notebooks and separate output directory |
revolut.business |
Revolut Business | Separate Revolut sandbox account and its own private files |
zeoconnect |
Hosted connection and pairing | Fake service or separately paired test identity/resources |
gemini.images |
Gemini keys and host custody | Offline request/provider fixtures or separate Google project |
notebook |
Notebook execution | Local synthetic notebook; no account or key |
The first seventeen rows are package entry points. ZEOconnect, Gemini images and
notebook execution are additional composition APIs. Their launcher selections
forward no provider keys: Gemini uses explicitly provisioned host custody and
notebook execution is local. The database.sqlite and database.bigquery directories
are placeholders with no implemented service or credential workflow; they are
not supported integrations. HTTP/MCP are adapters for exposing capabilities,
not additional provider accounts. Future integrations must join this inventory
and provide both tracks before their setup is considered complete.
Test mode is a ZeoCore environment selection. It does not turn an ordinary provider account into a vendor sandbox. Provider credentials, account permissions, selected resources and recipients still determine what the provider can change.
For staged notebook/document releases, use authoring conversion receipts.
For runtime-admitted meeting actions, use the meeting adapters.
Trusted notebook execution is a separate optional local API.
Run the complete authoring reference for a staged, independently checked release.