# OCNORA

> Coordinate AI, workflows and software delivery across your business. Connect 1,000+ cataloged app and cloud-service providers, run AI agents inside budgets and human approvals, audit every run, and deploy on our cloud, yours, or inside your own product.

- Name: OCNORA
- Category: workflow automation and AI-agent platform
- Category line: Coordinate AI, workflows and software delivery across your business.
- Company: KXN Technologies
- Domain: ocnora.ai

## What is OCNORA
The passages below are the ones on [What is OCNORA?](https://ocnora.ai/what-is-ocnora), built from the same source. Each names the claims-registry entries it states.

### What is OCNORA?
OCNORA is a workflow automation and AI-agent platform built by KXN Technologies (ocnora.ai). Its category line is “Coordinate AI, workflows and software delivery across your business.” It connects 1,075 cataloged app and cloud-service providers, runs AI agents inside token and USD budgets and human approvals, keeps a record of every run, and deploys on OCNORA Cloud, on the customer’s own cloud, or embedded in the customer’s product.
Sources: providers (providers; measured; checked 2026-09-22; source: src/data/providers-index.json#providerCount (npm run sync:catalog)); agentNode (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); aiBudgetUsage (budget model; unverified; checked 2026-09-28; source: coax-backend AI cost ledger, budget router and circuit breaker (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); humanApprovals (approval model; unverified; checked 2026-09-28; source: coax-backend human.prompt node and router (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); runAudit (audit model; unverified; checked 2026-09-28; source: coax-backend run store and audit log (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); deploymentOptions (deployment options; unverified; checked 2026-09-28; source: coax-backend deployment manifests: Docker Compose file and Helm chart (evidence register C14, C15, C22; E08, E09, E17 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-036)))

### Who is OCNORA for?
OCNORA is for IT operations teams automating requests, approvals and incident follow-up; engineering leaders coordinating software delivery and AI agents in validated workflows; data and platform teams moving data between warehouses, queues and cloud services on their own infrastructure; SaaS product teams embedding automation in their own product under their own brand; and security and procurement teams who need to know where secrets are kept, who can act, what AI can spend and what ran. Customers who have approved being named: SyncRivo, UpSkillZone and ATS Eye.
Sources: approvals (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); workflowHealth (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); composeAndHelm (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); embedJitSso (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); whiteLabel (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); encryptionBackends (key backends; unverified; checked 2026-09-27; source: coax-backend KMS adapters (local, GCP and AWS implemented; Azure Key Vault and HashiCorp Vault are stubs)); customerNames (named customers; unverified; checked 2026-09-28; source: OCNORA_WEBSITE_IMPROVEMENTS sheet, task WEB-000 (customer names approved for publication))

### How is OCNORA different?
In OCNORA the controls are part of the engine on every deployment rather than an add-on: every model call is written to a ledger with its tokens and USD cost and checked against monthly budgets per workspace and per provider (per tenant on Embedded); a human.prompt step holds a run until a person answers; Workflow Health validates each workflow on save and publish and a dry run executes the graph with side effects suppressed; and each run keeps its steps with input, output, status and the connection used. The same product can run on the customer’s own cloud under an offline signed licence with no phone-home, or be embedded in another product with JIT SSO and per-tenant budgets. It imports n8n workflow JSON. Comparisons with other platforms, each figure sourced and dated, are at https://ocnora.ai/compare.
Sources: aiBudgetUsage (budget model; unverified; checked 2026-09-28; source: coax-backend AI cost ledger, budget router and circuit breaker (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); humanApprovals (approval model; unverified; checked 2026-09-28; source: coax-backend human.prompt node and router (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); workflowHealth (health check model; unverified; checked 2026-09-28; source: coax-backend Workflow Health role, Auto Fix worker and the system-workflow-health template in coax-backend src/mantle/templates/data, which the site does not publish (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); dryRun (test mode; unverified; checked 2026-09-28; source: coax-backend Workflow Health dry run (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); runAudit (audit model; unverified; checked 2026-09-28; source: coax-backend run store and audit log (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033))); offlineLicence (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); embedJitSso (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); perTenantBudgets (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); n8nImport (n8n node types (approximate); unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read))

### How can OCNORA be deployed?
OCNORA runs on OCNORA Cloud, on the customer’s own cloud from the Docker Compose file or the Helm chart in the backend repository, or embedded in the customer’s product. The Helm chart runs each process role as its own deployment, including Workflow Health, Auto Fix and the task orchestrator. Self-hosted and embedded installations verify their licence offline and keep workflow data, run history and secrets in the customer’s own cloud account, region and database. Docker Compose and Helm are the only manifests; running the customer’s own cloud is the customer’s job.
Sources: deploymentOptions (deployment options; unverified; checked 2026-09-28; source: coax-backend deployment manifests: Docker Compose file and Helm chart (evidence register C14, C15, C22; E08, E09, E17 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-036))); offlineLicence (deployments; unverified; checked 2026-09-27; source: src/app/pricing/page.tsx feature matrix as published at 5405ddc (coax-backend not re-read)); dataHandling (processing region; unverified; checked 2026-09-28; source: coax-backend deployment manifests and offline licence check; evidence register C22 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-037))

### Which AI model providers does OCNORA support?
OCNORA wires 4 hosted model vendors for AI building and agents: Anthropic, OpenAI, Google and DeepSeek. Self-hosted and embedded installations can also use local models through any OpenAI-compatible inference server the customer hosts (vLLM, Ollama, LM Studio, llama.cpp). Every model call routed through OCNORA, whichever vendor serves it, is written to the cost ledger and checked against the token and USD budgets.
Sources: llmVendors (hosted LLM vendors; unverified; checked 2026-09-27; source: coax-backend AI vendor factory); localModels (deployments; implemented; checked 2026-10-20; source: coax-backend ai/providers/factory.py and ai/providers/openai_compatible_adapter.py (the openai_compatible provider)); aiBudgetUsage (budget model; unverified; checked 2026-09-28; source: coax-backend AI cost ledger, budget router and circuit breaker (evidence register C12, C13, C16; E07 (OCNORA_WEBSITE_IMPROVEMENTS task WEB-033)))

### How many integrations does OCNORA have?
OCNORA counts integrations in three units that are not interchangeable. Its public catalogue has 1,075 providers (the vendors and individual cloud services it connects to, one integration page each) and 7,621 documented node types: 7,378 belong to a provider and 243 are core node types (control flow, data, AI, files, vectors) that need no connection. 84 of the node types are triggers. A provider is not a node type, and neither is an “app” or an “integration” in another vendor’s sense. A service with no typed node is reached through the HTTP node with the customer’s own credential.
Sources: providers (providers; measured; checked 2026-09-22; source: src/data/providers-index.json#providerCount (npm run sync:catalog)); nodeTypes (node types; measured; checked 2026-09-22; source: src/data/providers-index.json#documentedNodeTypes (npm run sync:catalog)); providerNodeTypes (node types; measured; checked 2026-09-22; source: src/data/providers-index.json#nodeCount (npm run sync:catalog)); coreNodeTypes (node types; measured; checked 2026-09-22; source: src/data/providers-index.json#coreNodeTypes (npm run sync:catalog)); triggers (trigger types; measured; checked 2026-09-22; source: src/data/providers-index.json#triggerCount (npm run sync:catalog))

## Pages
- [What is OCNORA?](https://ocnora.ai/what-is-ocnora): what it is, who it is for, how it differs, deployment, model providers, integration units
- [Platform](https://ocnora.ai/platform): Build, Agents, Govern, Run, Deliver
- [Software delivery](https://ocnora.ai/platform/software-delivery): Task Runs, scoped engineering tasks on a runner you host, with your checks and human review
- [Controls and operations](https://ocnora.ai/platform/controls): human approvals, Workflow Health and repair paths, dry runs and their limits, run inspection and audit, AI budgets, role-based permissions
- [AI agents](https://ocnora.ai/ai): agent node, models, budgets, RAG, MCP, Build with AI
- [Enterprise](https://ocnora.ai/enterprise): deployment, architecture, multi-tenancy, access
- [Security](https://ocnora.ai/security): secrets, data, access, audit, disclosure
- [Pricing](https://ocnora.ai/pricing): Cloud, Self-hosted, Embedded, Enterprise
- [Integrations](https://ocnora.ai/integrations): 1075 providers
- [Templates](https://ocnora.ai/templates): 40 curated templates
- [Blog](https://ocnora.ai/blog): working notes on building, governing and running automations
- [Resources](https://ocnora.ai/resources): guides, templates, comparisons, changelog, reference
- [Compare](https://ocnora.ai/compare): OCNORA next to other automation platforms
  - [OCNORA vs n8n](https://ocnora.ai/compare/n8n): every n8n figure quoted from n8n's own pages (5 sources, each dated)
  - [OCNORA vs Zapier](https://ocnora.ai/compare/zapier): every Zapier figure quoted from Zapier's own pages (4 sources, each dated)
  - [OCNORA vs Make](https://ocnora.ai/compare/make): every Make figure quoted from Make's own pages (4 sources, each dated)
  - [OCNORA vs Workato](https://ocnora.ai/compare/workato): every Workato figure quoted from Workato's own pages (7 sources, each dated)
  - [OCNORA vs Microsoft Power Automate](https://ocnora.ai/compare/power-automate): every Microsoft Power Automate figure quoted from Microsoft Power Automate's own pages (5 sources, each dated)
  - [OCNORA and Google Cloud Workflows](https://ocnora.ai/compare/google-cloud-workflows): every Google Cloud Workflows figure quoted from Google Cloud Workflows's own pages (7 sources, each dated)
  - [An n8n alternative with governance in the engine](https://ocnora.ai/alternatives/n8n): why teams look for a n8n alternative, how OCNORA answers each reason, and how the move works
  - [A Zapier alternative for automation run as infrastructure](https://ocnora.ai/alternatives/zapier): why teams look for a Zapier alternative, how OCNORA answers each reason, and how the move works
  - [A Make alternative with approvals and AI budgets built in](https://ocnora.ai/alternatives/make): why teams look for a Make alternative, how OCNORA answers each reason, and how the move works
- [Contact](https://ocnora.ai/contact)

## Feeds
- [Blog RSS](https://ocnora.ai/blog/rss.xml) · [Blog Atom](https://ocnora.ai/blog/atom.xml)
- [Changelog RSS](https://ocnora.ai/changelog/rss.xml) · [Changelog Atom](https://ocnora.ai/changelog/atom.xml) — one entry per day that shipped

## Integration groups
- Amazon Web Services: 394 providers
- Google Cloud: 152 providers
- Microsoft Azure: 182 providers
- AI & models: 12 providers
- Databases & warehouses: 32 providers
- Chat & messaging: 33 providers
- Files & storage: 13 providers
- CRM & sales: 35 providers
- Email: 22 providers
- Voice & SMS: 8 providers
- Developer & APIs: 1 providers
- Business apps: 191 providers

## Node reference
Each of the 7,378 node types that belong to a provider has a reference page
at https://ocnora.ai/integrations/<provider>/<node>:
what it does, the connection it needs, a config field table (type, required, default,
constraints, example), the shapes it emits with a sample, and related nodes. The node slug is
the node type with dots and underscores replaced by hyphens, so `slack.post_message` is
https://ocnora.ai/integrations/slack/slack-post-message.
The remaining 243 documented node types are core ones (control flow, data, AI, files, vectors)
that need no connection and have no page here yet. The pages that exist are listed in [llms-nodes.txt](https://ocnora.ai/llms-nodes.txt) and in [sitemap.xml](https://ocnora.ai/sitemap.xml);
they are too many to inline here. Catalogue 668a0cb515f936bd, synced 2026-09-22.
The 30 providers with the most nodes:
- [Google Compute Engine](https://ocnora.ai/integrations/compute-engine): 286 operations, 0 triggers
- [Snowflake](https://ocnora.ai/integrations/snowflake): 105 operations, 0 triggers
- [Google Cloud SQL Admin](https://ocnora.ai/integrations/cloud-sql-admin): 80 operations, 0 triggers
- [Google Cloud KMS](https://ocnora.ai/integrations/cloud-kms): 72 operations, 0 triggers
- [GitHub](https://ocnora.ai/integrations/github): 65 operations, 1 triggers
- [Google Artifact Registry](https://ocnora.ai/integrations/artifact-registry): 66 operations, 0 triggers
- [Pipedrive](https://ocnora.ai/integrations/pipedrive): 61 operations, 1 triggers
- [Google Firestore](https://ocnora.ai/integrations/firestore): 61 operations, 0 triggers
- [Google Cloud Monitoring](https://ocnora.ai/integrations/cloud-monitoring): 56 operations, 0 triggers
- [HubSpot](https://ocnora.ai/integrations/hubspot): 53 operations, 1 triggers
- [Freshworks CRM](https://ocnora.ai/integrations/freshworks-crm): 53 operations, 0 triggers
- [Google Cloud Build](https://ocnora.ai/integrations/cloud-build): 53 operations, 0 triggers
- [Google Cloud Run](https://ocnora.ai/integrations/cloud-run): 49 operations, 0 triggers
- [Copper](https://ocnora.ai/integrations/copper): 47 operations, 1 triggers
- [Slack](https://ocnora.ai/integrations/slack): 46 operations, 1 triggers
- [Stripe](https://ocnora.ai/integrations/stripe): 43 operations, 1 triggers
- [Mautic](https://ocnora.ai/integrations/mautic): 41 operations, 1 triggers
- [Google BigQuery](https://ocnora.ai/integrations/bigquery): 39 operations, 0 triggers
- [Google Cloud DNS](https://ocnora.ai/integrations/cloud-dns): 39 operations, 0 triggers
- [MISP](https://ocnora.ai/integrations/misp): 39 operations, 0 triggers
- [Contentful](https://ocnora.ai/integrations/contentful): 38 operations, 0 triggers
- [Freshservice](https://ocnora.ai/integrations/freshservice): 38 operations, 0 triggers
- [Google Kubernetes Engine](https://ocnora.ai/integrations/gke): 38 operations, 0 triggers
- [TheHive](https://ocnora.ai/integrations/thehive): 38 operations, 0 triggers
- [Jira](https://ocnora.ai/integrations/jira): 36 operations, 1 triggers
- [Matrix](https://ocnora.ai/integrations/matrix): 37 operations, 0 triggers
- [Shopify](https://ocnora.ai/integrations/shopify): 35 operations, 1 triggers
- [Paddle](https://ocnora.ai/integrations/paddle): 35 operations, 0 triggers
- [ClickUp](https://ocnora.ai/integrations/clickup): 33 operations, 1 triggers
- [Google Pub/Sub](https://ocnora.ai/integrations/pubsub): 34 operations, 0 triggers

## Blog
- [What 1,075 integrations actually counts: providers, operations and connections](https://ocnora.ai/blog/integration-catalog-coverage) (2026-09-28): What 1,075 providers means on OCNORA: how providers, operations and triggers are counted, where cloud services fit, and what one connection drives.
- [How to decide which support actions an AI agent may take alone](https://ocnora.ai/blog/ai-support-human-approval) (2026-09-28): Classify the ticket, fence the agent’s tools, treat confidence as a routing input and put a person, a timeout and a fallback in front of the risky step.
- [How a bug report becomes a reviewed change on your own runner](https://ocnora.ai/blog/bug-report-to-reviewed-change) (2026-09-28): How OCNORA Task Runs take a bug report through intake, a Git worktree on your runner, your own checks, blocked states and a person’s review before anything merges.
- [How to move CSV data into a SQL table and know the transfer was correct](https://ocnora.ai/blog/csv-to-sql-with-reconciliation) (2026-09-28): Map the columns, check the types, key the rows, batch and retry the writes, then compare counts and checksums on both sides and give rollback to a named owner.
- [What to check when you import an n8n workflow into OCNORA](https://ocnora.ai/blog/n8n-import-review-checklist) (2026-09-28): Credentials, expressions, branches, placeholder steps and Code nodes: what the n8n importer carries across, what it leaves to you, and how to run the first test.
- [Plan an application migration as a series of workflows](https://ocnora.ai/blog/application-migration-workflow-plan) (2026-09-28): Inventory, dependency checks, tests, transfer, validation, a cutover gate and a rollback owner: what orchestration does in a migration, and what it does not.
- [Run a cloud operations workflow across services, with credentials and an approval](https://ocnora.ai/blog/cloud-operations-workflow) (2026-09-28): One scoped cloud operations example: the AWS permissions it needs, request limits, the error path and a person’s approval before the workflow scales anything.
- [Embed workflow automation in your product: where identity, tenants and support sit](https://ocnora.ai/blog/embedded-automation-architecture) (2026-09-28): Where identity and tenant boundaries sit when you embed OCNORA: the token handoff, roles, connections, tenant setup, support and who runs the installation.
- [How to test a workflow before it touches anything real](https://ocnora.ai/blog/test-a-workflow-before-production) (2026-09-20): Static validation, a dry run against real config with side effects held back, then a first live run on one record. A practical order for shipping automations safely.
- [How to keep an AI agent’s spending close to the number you set](https://ocnora.ai/blog/keep-ai-agent-spending-under-control) (2026-09-20): A retry loop, a huge tool result or a growing prompt can turn one agent into a runaway bill. Here’s how per-tenant budgets and a circuit breaker limit it.
- [How much a dry run actually proves before you trust it live](https://ocnora.ai/blog/what-a-dry-run-actually-proves) (2026-09-20): A dry run executes your workflow with side effects suppressed and shows each step’s output shape. That shows the path resolves, not that the result is right.

## Templates
- [Q&A over a fetched document](https://ocnora.ai/templates/ai-doc-qa): Answer a question about any public document: fetch it over HTTP, hand the text plus the question to an LLM with a grounding prompt, and post the answer to a callback URL.
- [Document extraction to API](https://ocnora.ai/templates/ai-document-extraction): Receive a PDF (base64) by webhook, parse it, extract structured fields with a JSON schema, reshape them and POST the record to your API.
- [Inbox triage: classify and route email](https://ocnora.ai/templates/ai-email-triage): Every 15 minutes, fetch the next unread email, classify it (urgent / billing / general) and route urgent ones to the on-call inbox with an auto-acknowledgement.
- [AI support agent with order lookup](https://ocnora.ai/templates/ai-support-agent-email): A webhook hands a customer message to a tool-using agent that can look up the order over HTTP, then the answer is emailed back.
- [Form submission to Airtable with a Slack ping](https://ocnora.ai/templates/airtable-form-intake-with-alert): An intake form writes the submission to Airtable and tells the channel it landed.
- [Nightly Airtable view to a Google Sheet](https://ocnora.ai/templates/airtable-nightly-sheet-sync): Copy an Airtable view into a Google Sheet every night so anyone can pivot it without an Airtable seat.
- [New Airtable record to a HubSpot contact](https://ocnora.ai/templates/airtable-record-to-hubspot-contact): A record added to an Airtable base becomes a HubSpot contact, so the list people keep by hand reaches the CRM.
- [Nightly CSV feed to SQL](https://ocnora.ai/templates/data-csv-sync-to-sql): Download a CSV export every night, parse it, normalise the columns with the Process engine and upsert into a table.
- [Fan out a list to an API](https://ocnora.ai/templates/data-fan-out-http): Receive a list of items by webhook and call an API once per item, five in parallel, continuing past individual failures.
- [AI screen, human approve, then send](https://ocnora.ai/templates/hitl-approval-gate): Classify an inbound request, ask a reviewer to approve or reject it, and email the requester the outcome.
- [Extract with human clarification on low confidence](https://ocnora.ai/templates/hitl-extract-with-clarification): Extract structured data from text; when the model is unsure it pauses and asks a person to pick from candidates, then the record is posted.
- [Closed-won HubSpot deal to a spreadsheet](https://ocnora.ai/templates/hubspot-deal-won-to-sheet): Every deal that changes stage is read back and appended to a Google Sheet for finance.
- [Welcome e-mail for a new HubSpot contact](https://ocnora.ai/templates/hubspot-new-contact-welcome): When a contact is created in HubSpot, read it back and send a personalised welcome e-mail.
- [Failed payment to a HubSpot ticket and a Slack alert](https://ocnora.ai/templates/hubspot-ticket-from-failed-payment): A Stripe payment failure opens a HubSpot ticket against the customer and pings the billing channel.
- [First notice of loss: extract, validate, triage](https://ocnora.ai/templates/insurance-fnol-triage): A claim notification arrives by webhook; AI extracts the loss details, the payload is validated, an adjuster triages it and the claim is opened in Iris.
- [Jira issue updates to a Microsoft Teams channel](https://ocnora.ai/templates/jira-issue-to-teams): Created and updated Jira issues are announced in the Teams channel the squad actually watches.
- [Bug report webhook to a Jira issue](https://ocnora.ai/templates/jira-webhook-bug-intake): Let any tool — a status page, a form, your app's crash handler — raise a Jira issue over one webhook.
- [Form submission to a Notion database](https://ocnora.ai/templates/notion-form-to-database-page): A public intake form writes one page per submission into a Notion database.
- [Mirror new Jira issues into Notion](https://ocnora.ai/templates/notion-jira-bug-mirror): Every issue Jira raises is mirrored as a page in a Notion database, for people who live in Notion.
- [Weekly Notion database digest to Slack](https://ocnora.ai/templates/notion-weekly-digest-slack): Query a Notion database on a schedule and post what it holds into a Slack channel.
- [Scheduled health check with email alert](https://ocnora.ai/templates/ops-http-health-check): Ping an endpoint every 5 minutes; if it does not return 200, email the on-call address with the status code.
- [Validated webhook to database](https://ocnora.ai/templates/ops-webhook-validate-upsert): Accept events by webhook, reject malformed payloads with a JSON schema, and upsert the valid ones into a SQL table.
- [Sales inbox: qualify and route](https://ocnora.ai/templates/sales-inbox-lead-router): Poll the sales mailbox, classify each email as lead / existing customer / vendor, create Iris records for new leads and forward the rest to the right team.
- [Salesforce case to a Jira issue](https://ocnora.ai/templates/salesforce-case-to-jira): Every new Salesforce case is raised as a Jira issue so engineering works from one queue.
- [New Salesforce lead to Slack](https://ocnora.ai/templates/salesforce-new-lead-to-slack): Poll Salesforce for new leads and post each one into the sales channel as it arrives.
- [Weekly Salesforce pipeline digest](https://ocnora.ai/templates/salesforce-pipeline-digest-email): Run a SOQL query against open opportunities every Monday and e-mail the result to the sales lead.
- [Daily spreadsheet summary by e-mail](https://ocnora.ai/templates/sheets-daily-summary-email): Read a range from a Google Sheet every morning and e-mail the rows to a distribution list.
- [New spreadsheet row to a HubSpot contact](https://ocnora.ai/templates/sheets-row-to-hubspot-contact): A new row in a Google Sheet becomes a HubSpot contact, and the team hears about it in Slack.
- [Webhook to a spreadsheet row](https://ocnora.ai/templates/sheets-webhook-append-row): Log every webhook POST as a row in a Google Sheet — the simplest durable audit trail there is.
- [Internal request form to a Slack channel](https://ocnora.ai/templates/slack-form-request-to-channel): A public request form posts every submission into a Slack channel, formatted and ready to pick up.
- [Daily Jira bug digest to Slack](https://ocnora.ai/templates/slack-jira-bug-digest): Every morning, search Jira for open bugs and post the count and the list to a Slack channel.
- [Incident webhook to Slack and Microsoft Teams](https://ocnora.ai/templates/slack-teams-incident-broadcast): One webhook from your monitoring tool announces the incident in both Slack and a Teams channel.
- [Stripe payment failure alert](https://ocnora.ai/templates/stripe-failed-payment-alert): A failed Stripe payment reaches the billing channel and the billing inbox with the customer already looked up.
- [Monthly Stripe invoice summary to a spreadsheet](https://ocnora.ai/templates/stripe-invoice-summary-sheet): List the month's paid invoices and append the totals to a Google Sheet finance already reads.
- [New Stripe customer to an Airtable record](https://ocnora.ai/templates/stripe-new-customer-to-airtable): Every customer Stripe creates is written into an Airtable base so non-engineers can work the list.
- [Teams channel message to a Jira issue](https://ocnora.ai/templates/teams-message-to-jira): A message in a watched Teams channel raises a Jira issue, so an ask in chat does not get lost.
- [Daily standup digest from Notion to Teams](https://ocnora.ai/templates/teams-notion-standup-digest): Query the standup database in Notion each morning and post it to the team's Teams channel.
- [Delay, retry and dead-letter](https://ocnora.ai/templates/util-delay-retry-webhook): Call a flaky endpoint with backoff retries; on final failure wait, try a fallback endpoint, and if that also fails email an operator.
- [Scheduled API digest by email](https://ocnora.ai/templates/util-scheduled-report-email): Every weekday morning pull a JSON summary from your API, have an LLM turn it into three bullet points and email the team.
- [Webhook transform and forward](https://ocnora.ai/templates/util-webhook-transform-forward): Receive any JSON, normalise a few fields, reshape it and forward to another endpoint — the smallest useful glue workflow.