“I’m using the HTTP Request step to call Firecrawl.

Hi @phlipineck,

You are very close. The HTTP Request step exposes three values: status (the HTTP code), body (the raw response text) and json (the body already parsed as JSON). Everything inside the response lives under that json value, so with the Firecrawl structure you posted the path is:

{{ http_request1.json.data.metadata.title }}

Your attempts were skipping the json part, which is why the value came back empty and the next step complained that its title was missing.

Two small things that make this easier next time. After a test run, click the HTTP Request step: the panel on the right shows the full output of the last run (status, body and json), so you can see exactly what Firecrawl returned and work out the path from there. And the Log Message step only reports “logged” because the message itself goes to the log file (Settings → For developers), not to the canvas, so the inspector is the quicker place to look at the response.

Also double check the step ID shown in the inspector: it is http_request1 for the first HTTP step you add, but it becomes http_request2 if you added one before, or something else if you renamed it.

Hope that gets your workflow running, and thanks for trying Meow Workflow this early! 😊

Cheers,
Jordy.

Hi Phil,

Thank you for the details, and sorry for the hours lost. I reproduced both problems on a WordPress 7.1 site, and both are on my side, not yours.

Problem 1, the blank Webhook URL. The URL is actually there. The WordPress admin styles give read-only fields a light grey background, and my field uses light text, so the URL ends up light on light and invisible. Version 0.1.3, released today, makes it visible again. Until you update, click inside the empty-looking field and press Ctrl+A then Ctrl+C (Cmd on Mac), or use the copy button on its right: the full URL is in the clipboard.

Problem 2, the Firecrawl “Invalid URL”. The trigger hint in the plugin says the body is exposed as trigger.body, but the fields of your payload actually sit directly on trigger. So in the HTTP Request body, replace {{ trigger.body.url }} with:

{{ trigger.url }}

Firecrawl was receiving an empty url, hence the error and the null output. In 0.1.3 the hint is corrected, trigger.body works as well (so your current expression is fine too once updated), and the “required input is missing” error now tells you which reference came back empty. Please try the new 0.1.3 version.

Once Firecrawl answers, the title is at {{ http_request1.json.data.metadata.title }} as mentioned before. If anything else gets in the way, tell me here and I will look at it right away.

Thanks again for your patience, and for pushing Meow Workflow this far! 😊
Jordy.

Indexes are written with a dot, not brackets, so the path is:

{{ gemini.json.candidates.0.content.parts.0.text }}

That works in 0.1.3 right now. Brackets like candidates[0] were silently ignored, which is why everything came back empty. Version 0.1.4 (I have released it now) accepts the bracket form too, and after a test run the Insert data menu lists every nested field of the response with its value, so you can click the exact path instead of typing it. It also shows a step’s last output right at the top of the panel when you click it, so what an API returned is never hidden again.

About {{ gemini.json }} on its own: in 0.1.3 a whole JSON object dropped into a text field comes out empty. 0.1.4 turns it into JSON text. Until then, {{ gemini.body }} gives you the same content as raw text.

And thanks for the note on the webhook URL. If it is still faint after a hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on Mac), the browser is holding the old script. In 0.1.4 the URL is shown as plain text in a light box that wraps on several lines, so nothing can hide it again.

Thanks for testing all this so thoroughly, it is making the plugin better for everyone 😊

Cheers,
Jordy

You’re very welcome @phlipineck 😊 And feel free to leave a little review if you can, it really helps! No reviews means no downloads, and the more I get, the more motivated I am to keep working on it. Thank you!