Integrations · Coda
Guild agents read and write Coda documents, manage table rows, govern permissions, and handle Pack lifecycle tasks on your behalf. Guild stores the Coda API key server-side and injects it into every request, so agent code never sees the credential. Credential policies let you restrict which operations each agent can call, and every request runs through Guild’s audit trail.
Book a demo
See how teams govern agents that use Coda.
Talk to sales
Get access to Guild, then connect Coda to your first agent.
What the Coda integration exposes
The integration isguildai~coda-openapi and authenticates with a Coda API key sent as a bearer token. Tools cover document and page management, table and row operations, formula retrieval, ACL and permission management, doc publishing with custom domains, analytics, and Pack lifecycle tasks including releases, reviews, invitations, and ingestion logs. Use pick() to give an agent only the tools it needs.
How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in Guild. Click Connect, search for coda-openapi, and select it.
2
Paste your Coda API key
Enter your Coda API key in the API Key field. Guild stores it and sends it as a bearer token in the
Authorization header on every request.3
Import tools into your agent
Import
CodaOpenapiTools from @guildai-services/guildai~coda-openapi and spread it into your agent’s tools object. Tools follow the coda_openapi_ prefix convention.Why Coda access needs governing
Coda tools can delete docs and pages, modify table data, change ACL settings, publish docs to custom domains, and alter Pack permissions. A single credential with no controls could let any agent in the workspace make any of those changes. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request leaves Guild, scoped to specific agents, workspaces, or operations using exact names or wildcard patterns such ascoda_openapi_delete_*.
Guild injects the credential server-side after the policy check passes, so agent code never receives the API key. You can scope a credential to one workspace, one member, or one agent using the options on the Credentials page, and the workspace-restriction setting blocks agents from falling back to the account-level credential. Agents with broad access contrast with agents locked to read-only operations such as coda_openapi_get_* and coda_openapi_list_*.
About the Coda integration
Agents can read and write Coda documents, including creating and deleting pages, managing table rows and columns, and retrieving formula results. They can also manage doc and Pack permissions, publish docs with custom domains, and access analytics data. Pack management tasks such as creating releases, handling reviews, and configuring permissions are also supported. The integration isguildai~coda-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Coda
In Guild, go to Access & setup > Credentials, click Connect, select coda-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thecoda_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~coda-openapi:
All 125 tools
All 125 tools
Frequently asked questions
Can a Guild agent trigger a Coda automation by webhook?
Can a Guild agent trigger a Coda automation by webhook?
No. The catalog entry for
guildai~coda-openapi lists no webhook events. The integration exposes coda_openapi_trigger_webhook_automation, which sends a request to a webhook-invoked automation in Coda, but Guild does not receive inbound webhook events from Coda.How do I stop an agent from deleting Coda docs or pages?
How do I stop an agent from deleting Coda docs or pages?
Write a DENY rule in the credential policy targeting
coda_openapi_delete_doc and coda_openapi_delete_page, or use the pattern coda_openapi_delete_* to block all deletion operations. Guild’s credential proxy enforces the rule before any request reaches Coda. See credential policies for syntax.Can different agents use different Coda accounts?
Can different agents use different Coda accounts?
Yes. Connect a dedicated credential for a specific agent from the installed agent’s page, or scope a credential to a single workspace. Guild resolves credentials in order: grants and dedicated credentials take priority over workspace and account defaults. See Credentials for the full resolution order.
Does the agent code see the Coda API key?
Does the agent code see the Coda API key?
No. Guild stores the key and injects it as a bearer token server-side, after credential policies pass. The key never enters agent code, the container, the prompt, or agent state.
Put a governed agent on Coda this week
Book a demo
See how teams govern agents that use Coda.
Talk to sales
Get access to Guild, then connect Coda to your first agent.