Integrations
How Open Technology App connects to systems you already use, and which plans include each one.
API keys
Platform-owner managedLegacy keys support selected endpoints. They are shown once and stored as hashes. They do not provide general project-scoped project/item CRUD; scoped machine credentials remain planned.
Inbound webhooks
Starter and ProPer-project endpoints that create or update items from an external system. Requests are HMAC-signed; the shared secret is shown once. Field mapping, a title template, and an optional dedup field control how the payload becomes an item.
DB sync
Hosted and self-hostedPull from PostgreSQL, MySQL, REST APIs, or Google Sheets into a queue on a schedule.
Email inbound
Hosted and self-hostedRoute inbound email to a queue as new items or replies on existing ones. Requires connecting a mailbox provider in Admin settings.
Chrome extension
All plansQuick-add items from any page, scrape a table into a queue, and an AI sidebar for drafting content. Signs in with your existing account.
AI provider connections
All plansCustomer-provided Anthropic, OpenAI, or Hugging Face connections, configurable per organization. The App does not bill for AI usage — you connect and pay your own provider account.
Setup by role, API limits, and the scoped-access roadmap →
AI setup, security, scope and usage →
Credential handling and access requirements differ by integration. Review the supported connection and your permissions before supplying a credential.