Platform
Integrations and API
Generate a token and Geodocs talks to the tools you already use.
In Settings you create an access token with the scope you choose. With it, any tool can read projects, tasks, expenses and budgets: Zapier, n8n, Make, a Python script or your in-house ERP. The other way round, webhooks tell your system as soon as something is created, updated, archived or deleted.
- Access token with scope, expiry and last use visible
- Read API for projects, tasks, expenses, budgets and statuses
- Webhooks across 13 events, with signed delivery and a log of attempts
- Works with Zapier, n8n, Make and any tool that can make an HTTP request
Wiring up Zapier or n8n takes minutes
Both follow the same path. To read: generate the token in Geodocs and point the tool's HTTP request step at our API. To trigger: paste the flow's URL into Geodocs and pick which events should fire it. There is no need to wait for a marketplace connector, because any HTTP step already does the job.
- Reading: an HTTP request step with your token in the header
- Triggering: a Geodocs webhook firing the tool's flow
- A signature on every call, so your flow can confirm the source
- A limit of 100 requests per minute per token
AI agents come in the same way
The same token lets an AI agent of yours read the workspace, with the scope you define and nothing beyond it. Inside the product, the one already playing that role is Jos.IA, which answers about projects, hours and expenses while respecting the permissions of whoever asks.