Build it into anything
Connect any application, service, or workflow directly to Orgtools using our public API. Whether you're building custom automations with n8n, Workato, or Tray.io, or integrating with internal tools, simple HTTP requests with JSON responses work with any language or platform.
Authentication
Secure API key authentication with customizable headers for seamless integration. Every request declares a visibility of org_wide or restricted, so you control who can see what you send.
Ingest Source Facts (No Decision Created):
curl -X POST https://orgtools.com/api/v1/public/sources/
-H "X-API-Key: your-api-key-here"
-H "Content-Type: application/json"
-d '{
"content": "Q4 headcount plan: Engineering adds 6 roles, Support adds 2 roles.",
"title": "Q4 Headcount Plan",
"source": "Slack",
"visibility": "org_wide"
}'Create a Decision:
curl -X POST https://orgtools.com/api/v1/public/decisions/
-H "X-API-Key: your-api-key-here"
-H "Content-Type: application/json"
-d '{
"content": "We need to decide on the new feature prioritization...",
"title": "Q4 Feature Planning",
"source": "Product Team Meeting",
"visibility": "org_wide"
}'Set visibility to "restricted" and include restricted_to_emails (active org member emails) to limit a source or decision to specific people instead of the whole organization. The /sources/ endpoint also accepts a file upload in place of content: send multipart/form-data with a file field instead of a JSON body.
Common use cases
Here's how teams are using the Orgtools Public API:
n8n Workflows
Create powerful automation workflows in n8n that trigger decision creation from any connected service or data source.
Workato & Tray.io Integrations
Seamlessly integrate with enterprise automation platforms to create decisions from business processes and data flows.
Custom Applications
Integrate decision-making directly into your custom applications, internal tools, or business processes using any programming language.
Power Automate & Other Platforms
Works with Microsoft Power Automate, Integromat, and any platform that supports HTTP requests for maximum flexibility.
Configuration
Customize your API integration with flexible configuration options:
Custom API Key Headers - Use your preferred authentication header name. Once set, that header is the only one that authenticates the integration, so callers must switch to it.
Multiple Integrations - Create multiple API keys for different applications or environments
Visibility Controls - Every request declares org_wide or restricted visibility, with restricted grants scoped to specific teammates
Rate Limiting - 100 requests per hour per API key, with requests over the limit returning a 429
Usage Monitoring - Track API usage and performance metrics