Skip to content

docs: agents tutorial#8961

Merged
mendonk merged 28 commits into
mainfrom
docs-simple-agents-tutorial
Jul 11, 2025
Merged

docs: agents tutorial#8961
mendonk merged 28 commits into
mainfrom
docs-simple-agents-tutorial

Conversation

@mendonk
Copy link
Copy Markdown
Collaborator

@mendonk mendonk commented Jul 9, 2025

Preview build
Add a tutorial for connecting a JS application to an Agent.

Summary by CodeRabbit

  • Documentation
    • Added a new tutorial guiding users on how to connect a JavaScript application to a Langflow agent, including step-by-step instructions and code examples.
    • Updated the sidebar to include a "Tutorials" section under "Get started" for easier access to the new tutorial.

@mendonk mendonk requested review from aimurphy and melienherrera July 9, 2025 20:04
@mendonk mendonk self-assigned this Jul 9, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 9, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A new tutorial document was added, guiding users on connecting a JavaScript application to a Langflow agent, including flow setup and API interaction. The sidebar configuration was updated to include this tutorial under a new "Tutorials" section within the "Get started" category.

Changes

File(s) Change Summary
docs/docs/Tutorials/agent.md Added a new tutorial explaining how to connect a JavaScript app to a Langflow agent, including flow configuration and API usage.
docs/sidebars.js Updated sidebar to add a "Tutorials" category under "Get started" with a link to the new tutorial.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant JavaScript App
    participant Langflow API
    participant Langflow Agent

    User->>JavaScript App: Provides email input
    JavaScript App->>Langflow API: POST request with email as input
    Langflow API->>Langflow Agent: Passes input to agentic flow
    Langflow Agent->>Langflow API: Returns agent output (e.g., recommended items/URLs)
    Langflow API->>JavaScript App: Sends agent response
    JavaScript App->>User: Displays extracted URLs or recommendations
Loading

Possibly related PRs

  • docs: refresh quickstart #8582: Updates the quickstart guide to demonstrate running a simple agent flow and interacting with it programmatically, similar to the new tutorial's focus on API-based agent interaction.

Suggested labels

documentation, size:L, lgtm

Suggested reviewers

  • edwinjosechittilappilly
  • aimurphy
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs-simple-agents-tutorial

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@dosubot dosubot Bot added size:L This PR changes 100-499 lines, ignoring generated files. documentation Improvements or additions to documentation labels Jul 9, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 9, 2025
@github-actions

This comment was marked as outdated.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 9, 2025
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (3)
docs/docs/Tutorials/agent.md (3)

57-60: Bullet style violates markdown-lint rule MD004.

Switch * to - to stay consistent with the docs linter configuration.

-    * `LANGFLOW_SERVER_ADDRESS`: Your Langflow server's domain. The default value is `127.0.0.1:7860`. You can get this value from the code snippets on your flow's [**API access** pane](/concepts-publish#api-pane).
-    * `FLOW_ID`: Your flow's UUID or custom endpoint name. You can get this value from the code snippets on your flow's [**API access** pane](/concepts-publish#api-pane).
-    * `LANGFLOW_API_KEY`: A valid Langflow API key. To create an API key, see [API keys](/configuration-api-keys).
+    - `LANGFLOW_SERVER_ADDRESS`: Your Langflow server's domain. The default value is `127.0.0.1:7860`. You can copy this from the code snippets on your flow’s **API access** pane.
+    - `FLOW_ID`: Your flow’s UUID or custom endpoint name (also in the **API access** pane).
+    - `LANGFLOW_API_KEY`: A valid Langflow API key. Create one in **Configuration → API keys**.

113-118: Code block missing language identifier (MD040).

Add text (or console) so syntax highlighting isn’t triggered incorrectly.

-```
+```text
 URLs found:
 https://www.facebook.com/marketplace/108225782538164/electronics/
 https://www.facebook.com/marketplace/108944152458332/furniture/
 https://www.facebook.com/marketplace/137493719613732/kitchen-cabinets/

---

`153-154`: **Typo: “Which ever” → “Whichever”.**

```diff
-    Which ever approach you choose, your application receives three URLs for recommended used items based on a customer's previous orders in your local CSV, all without changing any code.
+    Whichever approach you choose, your application receives three URLs for recommended used items based on a customer’s previous orders in your local CSV—all without changing any application code.
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba9740f and d41b8a8.

⛔ Files ignored due to path filters (2)
  • docs/static/files/customer_orders/customer_orders.csv is excluded by !**/*.csv
  • docs/static/img/tutorial-agent-with-directory.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • docs/docs/Tutorials/agent.md (1 hunks)
  • docs/sidebars.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`docs/sidebars.js`: Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.

docs/sidebars.js: Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.

📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)

List of files the instruction was applied to:

  • docs/sidebars.js
`docs/docs/**/*.{md,mdx}`: All documentation content must be placed within the '...

docs/docs/**/*.{md,mdx}: All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
All documentation markdown files must start with a frontmatter block containing at least 'title' and 'description' fields.
Use admonitions (:::tip, :::warning, :::danger) in markdown files to highlight important information, warnings, or critical issues.
Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Use code blocks with language identifiers and optional titles for code examples in markdown documentation.
Documentation content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.

📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)

List of files the instruction was applied to:

  • docs/docs/Tutorials/agent.md
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/sidebars.js (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Sidebar and navigation should be kept current to ensure users can easily find all documentation sections and cross-references.
docs/docs/Tutorials/agent.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
🪛 markdownlint-cli2 (0.17.2)
docs/docs/Tutorials/agent.md

57-57: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


58-58: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


59-59: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


113-113: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


113-113: Code block style
Expected: indented; Actual: fenced

(MD046, code-block-style)


132-132: Code block style
Expected: indented; Actual: fenced

(MD046, code-block-style)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-and-deploy
🔇 Additional comments (1)
docs/sidebars.js (1)

10-16: Tutorial is discoverable—good addition.

The nested “Tutorials” category and reference to "Tutorials/agent" are wired correctly, so the new doc will appear under Get started → Tutorials.
No structural or naming issues spotted here.

Comment thread docs/docs/Tutorials/agent.md
Comment thread docs/docs/Tutorials/agent.md Outdated
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 9, 2025
@github-actions

This comment was marked as outdated.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 10, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jul 10, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@github-actions

This comment was marked as outdated.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 10, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jul 10, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

Copy link
Copy Markdown
Collaborator

@aimurphy aimurphy left a comment

Choose a reason for hiding this comment

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

2 small comments, otherwise good to go

Comment thread docs/docs/Tutorials/agent.md Outdated
Comment thread docs/docs/Tutorials/agent.md Outdated
@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jul 11, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 11, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jul 11, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

Copy link
Copy Markdown
Contributor

@melienherrera melienherrera left a comment

Choose a reason for hiding this comment

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

+1 Thank you for the changes. LGTM

@mendonk mendonk added this pull request to the merge queue Jul 11, 2025
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Jul 11, 2025
@mendonk mendonk enabled auto-merge July 11, 2025 01:28
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 11, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jul 11, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@mendonk mendonk added this pull request to the merge queue Jul 11, 2025
Merged via the queue into main with commit c30b81e Jul 11, 2025
13 checks passed
@mendonk mendonk deleted the docs-simple-agents-tutorial branch July 11, 2025 01:42
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 lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants