Hi all!
When I save the current database ‘thing’ to the parameter, it’s only showing a 5 digit code instead of the usual long unique ID?
This means that when I try and retrieve it from the URL, bubble can’t find it.
The parameter is the ‘surpriseme’. You can see ‘caterer’ showing correctly.
This is the action sending the database created ‘surprise me’ to the URL paramater
Based on the screenshots, you seems to be sending Scheduled Workflow ID [Result of Step 1] to “surpriseme” URL parameter instead of Database Thing’s unique ID
Are you creating the Database record within Backend Workflows?
Ahhh So it’s returning an API workflow ID and not the actual ID of the surprise me??
Correct, this id has nothing to do with what you are expecting.
An API workflow can not return data to the front end. To do so, you’ll need to call your own backend workflow through the API connector and get the return through there.
Yes, it might seem weird but that’s how it is.
Which action do I use in the workflow to start an API call?
1- create a backend api workflow and make it querryable from the internet
2- install the official API connector plugin
3- create a route inside API connector to call your API backend workflow
4- from your workflow, trigger the API connector route from the “plugin” tab.
Sorry to push for more of your knowledge - but I’m sat tearing my hair out!
I’m trying to set up the external API (never done this).
When I try to initliaise, it’s saying the paramaters are incorrect. I want to pull the ‘subject’ parameter into a front-end workflow, that’s why i’ve put ‘subject’ as a paramater.
The back-end workflow is surprise_me_creation
What does your backend workflow do?
It just creates a database thing called a ‘surprise me’ with various information like address etc.
I want to call the ID of the newly created ‘surprise me’ in the front-end so I can put it into the page URL to display the various information of that ‘surprise me’ on the page
Why do you need to use a backend workflow for that?
Just user a regular create a thing action on the page. Then you can access the thing itslelf in subsequent steps.
This is what I did in the end! Felt silly for not thinking of the simple option
