Skip to content

feat: add Tavily integration documentation and resources - #3478

Open
lakshyaag-tavily wants to merge 2 commits into
langfuse:mainfrom
lakshyaag-tavily:feat/add-tavily-integration-docs
Open

feat: add Tavily integration documentation and resources#3478
lakshyaag-tavily wants to merge 2 commits into
langfuse:mainfrom
lakshyaag-tavily:feat/add-tavily-integration-docs

Conversation

@lakshyaag-tavily

@lakshyaag-tavily lakshyaag-tavily commented Aug 6, 2026

Copy link
Copy Markdown

Summary

  • Add a Tavily integration guide at /integrations/other/tavily
  • Cover Tavily’s web capabilties
  • Demonstrate a simple OpenAI tool-calling agent with tavily_search and tavily_extract
  • Trace the agent, OpenAI calls, and Tavily tool calls with Langfuse
  • Add Tavily to the integrations sidebar and include the Tavily icon and trace asset

Validation

  • Validated the notebook format and Python syntax
  • Simulated the complete search → extract → final answer tool-calling flow
  • Ran Prettier formatting checks
  • Ran the H1 heading check

Greptile Summary

The PR adds an executable Tavily search-and-extraction integration tutorial, publishes it under the Other integrations section, and includes supporting visual assets.

  • Adds a traced OpenAI tool-calling agent using Tavily search and extract tools.
  • Routes the new notebook to /integrations/other/tavily and adds it to the sidebar.
  • Adds Tavily icon and trace-image assets.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking documentation-structure issue in the generated tutorial.

The notebook and generated MDX are synchronized and correctly routed, but the test-section heading is authored inside a code cell and therefore renders as code rather than page structure.

Files Needing Attention: content/integrations/other/tavily.mdx, cookbook/integration_tavily.ipynb

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  NB["Tavily notebook"] --> CONVERT["Cookbook conversion"]
  ROUTES["_routes.json"] --> CONVERT
  CONVERT --> MDX["Tavily integration MDX"]
  META["Other integrations meta.json"] --> PAGE["/integrations/other/tavily"]
  MDX --> PAGE
  ASSETS["Icon and trace assets"] --> PAGE
Loading
Prompt To Fix All With AI
### Issue 1
content/integrations/other/tavily.mdx:108
**Heading embedded in code block**

`Test the Tavily search tool` is authored inside the Python cell, so the generated page renders it as a code comment instead of a section heading and omits it from the page outline.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "feat: add Tavily integration documentati..." | Re-trigger Greptile

Context used:

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

@dosubot dosubot Bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Aug 6, 2026
@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown

@lakshyaag-tavily is attempting to deploy a commit to the langfuse Team on Vercel.

A member of the Team first needs to authorize it.

@review-notebook-app

Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@dosubot dosubot Bot added the documentation Improvements or additions to documentation label Aug 6, 2026
@CLAassistant

CLAassistant commented Aug 6, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants