HTTP / REST API

Before you connect HTTP / REST API

Authentication

Bearer token, API key, Username & password, Custom, OAuth 2.0, JWT — any one of these.

Connection test

Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

Prerequisites

• Optional — omit for a one-off literal-URL call. A SaaS connection needs no base_url: the catalog supplies the provider's API root and auth scheme.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

What you can do with HTTP / REST API

Operations, grouped by what they do to your data.

Nodes that use your HTTP / REST API connection

Beyond its own nodes, these generic nodes accept your HTTP / REST API credential. Each chooses the provider from the connection you select, so the same node also works with the other providers shown.

• Read RSS Feed
  rss.read
  Fetch an RSS or Atom feed and emit its entries in one normalised shape.

A sample HTTP / REST API workflow

1. 1
   A core trigger

   Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no HTTP / REST API trigger is needed.
2. 2
   HTTP Requesthttp.request

   Call an HTTP API — via a Connection's named API or a literal URL.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Templates that use HTTP / REST API

• Q&A over a fetched document

  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

  Receive a PDF (base64) by webhook, parse it, extract structured fields with a JSON schema, reshape them and POST the record to your API.
• Nightly CSV feed 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

  Receive a list of items by webhook and call an API once per item, five in parallel, continuing past individual failures.
• Extract with human clarification on low confidence

  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.
• First notice of loss: extract, validate, 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.
• Scheduled health check with email alert

  Ping an endpoint every 5 minutes; if it does not return 200, email the on-call address with the status code.
• Sales inbox: qualify and route

  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.
• Delay, retry and dead-letter

  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

  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

  Receive any JSON, normalise a few fields, reshape it and forward to another endpoint — the smallest useful glue workflow.

Where HTTP / REST API fits

HTTP / REST API questions

How does OCNORA authenticate with HTTP / REST API?

With a stored Bearer token or API key or Username & password or Custom or OAuth 2.0 or JWT credential. A connection test can check it when you add it.

What can I automate with HTTP / REST API?

1 typed operation, each with a reference page listing its config fields and the shapes it emits. The credential also drives 1 generic node.

What if the HTTP / REST API operation I need is not listed?

Where HTTP / REST API has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use HTTP / REST API?

Yes: 11 templates, listed above.

How are HTTP / REST API calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.