Skip to the operations

Research

Tavily in a decision flow.

1 Tavily operation a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Research
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

A search API built for language models.

Tavily searches the web and returns cleaned, source-attributed content sized for a model's context rather than a page of links. Its niche is retrieval for agents: fewer results, already extracted, with the sources kept so an answer can cite them.

What a flow can call

1 operation, each one a step you can place on the canvas.

  1. POST/search

    Search the web for analyst context

    Returns current web results for an analyst or internal research workflow.

Where it sits in the decision

Research calls have a natural place in a flow.

Open-web lookups supply the context that is not in any structured feed. They are the slowest calls in a flow and the least predictable, so they usually sit on a branch that has already decided the case is worth the wait.

Whatever Tavily returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Tavily as a connection authenticating with an API key.
  • 02Tavily has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Search the web for analyst context” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Tavily in a flow.

How do I connect Tavily to a decision flow?

Add Tavily as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Tavily in a decision without ever seeing the secret.

Can I test Tavily without touching production?

Tavily exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Tavily?

1 operation: “Search the web for analyst context”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Search the web for analyst context”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Tavily be called?

Open-web lookups supply the context that is not in any structured feed. They are the slowest calls in a flow and the least predictable, so they usually sit on a branch that has already decided the case is worth the wait.

Also in Research

Ready when you are

Wire Tavily into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs