How to Access Previous Step's Output (record.id, record.databaseId) in Webhook JSON Body?

[marco.h]

I try to send a Webhook to make.com
But i don´t know how the JSON must look that the recordId and datasheetId are send.

AITable the POST JSON to submit the recordId and datasheetId

{
   "recordId": "Step 1",
   "datasheetId": "Step 1"
}

I’m trying to send specific data from a previous step in my Bika automation flow to an external webhook (Make.com). I need to send the recordId and the datasheetId.

My flow has a step that successfully outputs the following data structure (example from a test run):

// Output from the step *before* the webhook step
{
  "database": {
    "id": "dat4is06xxxxxxxxxxxx",
    "name": "Sites",
    "url": "..." 
  },
  "record": {
    "id": "record_id", // <-- Need this value
    "databaseId": "dat4is06xxxxxxxxxxxx", // <-- Need this value
    "revision": 0,
    "cells": { ... }, // Cells details omitted for brevity
    "url": "..." 
  }
}

// Note: Sometimes the entire output might be wrapped in an array like [ { ... } ] 
// Please clarify if the access path changes in that case (e.g., needing [0]).

In the next step (“HTTP Request” / Webhook), I want to configure the JSON body like this:

{
  "datenblatt": "{{ VARIABLE_FOR_databaseId }}", 
  "reihe": "{{ VARIABLE_FOR_recordId }}" 
}

I tried using simple variables like {{recordId}} but they came through empty.

My question is: What is the exact variable syntax ({{…}}) I need to use in the JSON body to correctly reference:

1. The id from the record object (record.id)?

2. The databaseId from the record object (record.databaseId)?

Assuming the step providing the output is named previous_step_name, would it be something like {{ steps.previous_step_name.output.record.id }}? And what if the output is an array?

Thanks for your help!

[marco.h]

Find the solution: with / i got the variables

[Thea]

Hi @marco.h welcome to the Bika.ai community! Really glad to hear you figured it out using the / path — and thanks so much for sharing the full context. It’s super helpful for others who might be setting up similar webhook flows. We’re actively working on updating our Help Docs to make variable path usage clearer inside automation steps. Sorry for the confusion this time around!