One honest note before the answers. The lesson's test call used a placeholder key on purpose, so it shows Felo's own Invalid API Key answer. The email step then ran on pinned sample answers marked SAMPLE, which are made up. So this page tells you what the setup looks like and what Felo's docs say comes back, not what a real answer looked like. The example business, Lakeshore Bookkeeping and its owner Priya Nair, is made up too.
What does each node in the workflow do?
| Node | Name on the canvas | What it does |
|---|---|---|
| Schedule Trigger | Every Monday at 7am | Runs the workflow every week, Monday, 7:00 |
| Code | This week's questions | Returns one item per question |
| HTTP Request | Ask Felo | POSTs each question to Felo |
| Code | Build the brief | Pairs answers with questions, keeps 3 sources each |
| Gmail | Email the brief | Sends one HTML email to you |
Because the questions node returns one item per question, Ask Felo runs once for each. Three questions means three calls.
How is the HTTP Request node set up?
Open Ask Felo. The settings in the lesson are:
- Method: POST
- URL:
https://openapi.felo.ai/v2/chat - Authentication: Generic Credential Type, then Generic Auth Type: Bearer Auth
- Send Body on, as JSON, with this body:
{ "query": {{ JSON.stringify($json.question) }} }
The credential in the lesson is named Felo - add your key. You create it, paste your key into Bearer Token and save. n8n then sends the key as a bearer token on every call. If the HTTP Request node is new to you, the glossary entry covers the basics.
What does Felo send back?
According to Felo's Chat API docs, as the lesson reports them: a status, and data with answer (the text), query_analysis.queries (the searches it ran) and resources, a list of sources, each with a link, title and snippet. Build the brief reads data.answer and the first 3 entries in data.resources.
What does the Monday email look like?
Build the brief returns one item with a subject, such as Monday research brief, 2026-10-20, and an html body. Each question becomes a heading, then the answer, then a short Sources list of links. The email opens with one line: check the sources before you act on anything. In Email the brief, Subject is {{ $json.subject }}, Email Type is HTML and Message is {{ $json.html }}.
Try it free, step by step
n8n + Felo: A Monday Research Brief With a Source for Every Answer. Stop spending Monday morning searching. Every week n8n sends your questions to Felo's AI search API, gets back answers with their sources, and emails you one brief before work starts. Felo's free… You do every step yourself in a practice copy of n8n, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts.
Start the free lessonFrequently asked questions
- Where do I get a Felo API key?
Sign in at openapi.felo.ai with your Felo account and open API Keys. Give the key a name such as n8n and click Create Key. Copy it straight into an n8n credential. The API key entry explains why it is treated like a password.
- Where does the key go in n8n?
Only in a Bearer Auth credential, in the Bearer Token field. Never in the URL, the JSON body or a Code node. The downloaded workflow has no credentials in it, so you add your own after you paste it onto the canvas.
- Why does the lesson's test show Authorization failed?
The test used a placeholder in the credential, so Felo answered Authorization failed and Invalid API Key. That is useful: it means n8n reached Felo and Felo read the header, so the URL, method and Bearer Auth setup are right. Only the key is missing. Paste your key in and run it again.
- Why use JSON.stringify in the body?
It turns the question into a safe JSON string. A question with a quote mark in it would break a body you typed by hand. The JSON entry shows what a valid body looks like.
- Did the lesson show a real Felo answer?
No. No key was created and no email was sent. The answers you see in Build the brief are pinned sample answers marked SAMPLE, written in the shape Felo's docs give. Your first real run is the first time you will see Felo's own text.
- What are the pinned sample answers for?
Pinned data lets you test the nodes after Ask Felo without calling Felo. The canvas after the test run shows the sample answers pinned on Ask Felo. When your key is in place, unpin them so a test uses Felo's real answers.
- Can I change the questions or the day?
Yes. Edit the list in This week's questions: one line per question. Change the day and hour in Every Monday at 7am. The workflow's time zone is New York, which you can change in the workflow settings (see workflow time zone).
- How many questions can I add?
Each question is one Felo API call, so check Felo's own API docs for usage terms before you add more questions or run it daily.
- Can I trust the answers in the email?
Treat them as a starting point. Felo answers from live AI search and returns its sources, which is why the brief keeps 3 links per answer. Open the link before you act on a rule change or a price. The Felo research mistakes guide shows why a cited source can still be second-hand.
- How do I turn it on?
Put your own address in To, click Execute and read the test email. Keep the workflow off until it looks right, then click Publish so it runs every Monday.
- Is this an official Felo course?
No. It is Stepthrough's own lesson. Felo is a separate product from felo.ai. For how the Felo app itself works, see the Felo AI search FAQ.
Key takeaways
- Five nodes: Schedule Trigger, a questions Code node, one HTTP Request to Felo, a brief-building Code node and Gmail.
- Ask Felo is POST to
https://openapi.felo.ai/v2/chatwith a Bearer Auth credential and a one-field JSON body. - Invalid API Key in a test means the setup is right and only the key is missing.
- The lesson's brief ran on pinned SAMPLE answers. Your first real answer comes after you add your key.
- Keep the 3 source links in the email and open them before you act.
For the common setup errors, read the n8n Felo research brief mistakes, keep the cheat sheets handy, or start the lesson.
