Skip to main content

Honeybase documentation

Honeybase is a workflow-automation platform: you design processes, release them as workflows, and each execution is a run. Around that sit human tasks, teams, schedules and availability, and AI agents.

These docs cover the two surfaces you integrate with from outside the app.

GraphQL API​

One endpoint, one organization API key. Everything the app can do with your data — tasks, processes, runs, teams, schedules, availability, agents — is reachable from POST /api/graphql with a hbk_ key.

  • Authentication — creating a key, sending it, what keys cannot do
  • Conventions — ids, dates, JSON-in-string fields, permissions
  • Pagination — limit / offset and when to prefer a point lookup
  • Errors — the errorType values and which are worth retrying
  • Examples — runnable curl calls
  • Schema reference — every type, query and mutation, generated from the schema

Integrations​

Connections to the systems your workflows read from and write to: databases, Slack, WhatsApp, email, Google Sheets, any HTTP API, and the LLM provider that powers the AI features. One page per integration type, listing exactly which settings the setup form collects and which credentials you need to obtain first.

Two things worth knowing up front​

Credentials never live in your workflow definitions. Secrets go to a dedicated secret store when you create the connection; workflow nodes reference the connection, not the credential. Reading a connection back through the API returns its configuration with secret values masked.

Everything an API key does is attributed to that key. Task writes made with a key show the key's name in the task's audit trail — you do not impersonate a user, and you cannot.