We’ve built a multi-screen Adalo app that collects user info (including dropdowns + image upload) into a collection called Hair Profiles V2.
On form submission:
It creates the record successfully
Then links to a “Webhook to Make” screen with a button to trigger a custom action webhook to Make.
The webhook fires… but it only sends the text string placeholders, not the actual field values (e.g. “{{ Current Hair Profiles V 2 > First Name }}”).
Make receives the request but no usable data — just literal Magic Text strings.
I’ve tried:
Linking the record to the “Webhook to Make” screen via the Submit button
Confirmed the DB record gets created
Using “Current Hair Profiles V2” in the custom action JSON body
Delaying the webhook (still doesn’t pass actual data)
Has anyone faced this timing issue where Adalo hasn’t fully populated Current data on the next screen yet?
What’s the best way to pass the actual record data to Make via webhook reliably?
Would massively appreciate any tips, workarounds or examples
Cheers,
Patrick
Sending data to Make via custom action isn’t usually an issue. How did you configure your custom action (screenshot may help)? Also how have you configured custom action on the button itself (screenshot may help)?
You’re right — it shouldn’t be an issue, which is why it’s driving me a bit mad.
Here’s the setup:
The form on the Home screen creates a record in Hair Profiles V2 .
On submit, it links to the “Webhook to Make” screen, passing the newly created record (as Current Hair Profiles V2)
That screen has a button called “Send to Make Test”
That button triggers a custom action with the webhook URL and JSON body using Magic Text from Current Hair Profiles V2
But when I test it — Make receives the request, but only gets the raw text like {{ Current Hair Profiles V2 > First Name }} instead of the actual values .
I’ll upload screenshots of both the custom action config and button action shortly — just wanted to summarise first in case it sparks any thoughts!
Thanks for your ChatGPT summary, but still without the screenshots it is not possible to understand what is happening. You can use tools like Loom for screen recordings as well.
The issue could be in the configuration of the custom action (there could be incorrect settings in the action itself); or in the data you’re passing to the custom action (the action call is misconfigured); or in the data availability on the screen; or in some unknown Adalo bug.
So as a starting point it is worthwhile to check if the custom action itself is created correctly (this is the most common mistake). I can not make any conclusion on this based on the information you’ve provided.
If first step is correct, second step will be to check if the custom action is called correctly. Again, I can’t see what data are you passing and how, so I can’t make any conclusion if this is set correctly or not.
If second step is correct, then we need to understand why the data is not passed correctly. The easiest way will be to replace magic text data with manually-entered values. If these values appear correctly in Make, then (obviously) there is some issue with getting magic text values.
This could be checked by adding labels on the same screen, and displaying magic text values there to check if they’re present or not.
If values are not present (which your chatGPT summary suggests), then you haven’t provided full information about your screen flow or there is a glitch in record creation. There are multiple other debug paths after this but I believe I’ve provided enough for now.
Thanks Victor, I sent the 5 screenshots before the ChatGPT summary email, they must have once again been delayed, or bounced back. Here is the text of my last email, with 1 screen shot added, to check that it get’s through to you:-
Sorry Victor, I did send some screenshots last night but I have just received an error message / bounceback, because I added 6 images and apparently as a non-paying user (at the moment), I am only allowed to add 5 – so here goes, I hope these screenshots help.
I think my custom action is not “bound” to a specific record. On the “Webhook to Make” screen, there’s a “Send to Make Test” button, but Adalo doesn’t know which Hair Profile record to use when that button is clicked.
The Magic Text selector says “Nothing Available” — there’s no record linked on that screen.
So Adalo just sends those literal placeholders like {{ Current Hair Profiles V2 > Age }} — which Make receives as strings, not actual values.
In an attempt to fix this, I am trying to pass the newly created Hair Profile record into the “Webhook to Make” screen as part of the link action after form submission, but I cannot find any way to do this (i.e. there is no link option available).
I attach some screenshots, but I am not sure which ones you want to see – so pleaselet me know if there are any particular screenshots you want.
The attached screenshots relate to the process I followed, outlined below.
I ran a test yesterday.
I started with a completely clean database (I deleted all records).
I submitted a test case with an image.
Test message came up and I checked the database, it shows 1 new record.
I checked the data received by Make and it still shows only text strings.
I went back to the API request form, still not able to add Magic Text.
Thanks Victor, I really appreciate your thoughtful and structured response — it’s very helpful.
To clarify:
The Custom Action is correctly configured with a valid webhook (I’ve tested it with static text and it reaches Make).
However, when I try to insert Magic Text (from the Hair Profiles V2 collection), the body of the Custom Action only receives the literal string placeholders, not the actual values.
I’ve already added text fields on the Webhook screen and those display the correct Magic Text values (e.g. “Enter TextPatrick”), which suggests the record is created and passed to the screen.
What’s not working:
In the Custom Action’s body, when I select Magic Text, I don’t get the option to use “Result of Step 1”.
I suspect this is because Adalo’s form Submit action doesn’t expose the created record in a way that the next action can reference it (which ChatGPT also confirmed).
Next step:
I’ll now rebuild the form manually using individual input components, and then use a custom button with:
Action 1: Create > Hair Profiles V2
Action 2: Link > Webhook screen + pass Result of Step 1
That should finally expose the correct Magic Text values to the Custom Action and fix the payload.
I’ll report back once I’ve done this — and will post a Loom walkthrough if the issue persists.
MirrorMe App: Data Flow Process (Option A)
Data saved to Hair Profiles V2 collection (confirmed)
Issue: No “Result of Step 1” data passed to next screen
But the screen isn’t receiving the correct record context
