Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick Update on Inngest blogpost #2909

Merged
merged 1 commit into from
Jan 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions blog/2025-01-07-inngest-ai-workflows/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Once those datasets are loaded into our Weaviate cluster, our workflow is trigge
Triggered by the above event, our Inngest agentic workflow goes through the following steps:


![An Inngest Workflow](./img/image1.png)
![An Inngest Workflow](./img/image3.png)

1. First, our workflow will retrieve some recipes from the `Thefoodprocessorcuisinetype` Weaviate collection.
2. Then, using the OpenAI `gpt-4` model, it will try to see if the food preferences contain some allergies.
Expand Down Expand Up @@ -258,7 +258,7 @@ export const generateMeal = inngest.createFunction(

Starting our dinner generator workflow with food preferences including `”no nuts”` triggers the `"query-ingredients-alternatives"` Weaviate query step based on the detection of the `"Allergies analysis"` LLM step.

![Architectural Diagram](./img/image3.png)
![Architectural Diagram](./img/image1.png)

The following steps of our Dinner generator workflow leverage Weaviate’s `collection.query.nearText()` and Inngest’s `step.ai.infer()` APIs similarly generate the menu, get the relevant wine pairing, and generate the shopping list.
Let’s now see our Dinner generator in action.
Expand Down
Loading