Hi! My name is Rick
I’ve recently started using Bubble and I’m running into an issue with a step in my workflow. It seems that the information is not being saved when a new record is created in my database.
"I have a workflow: Button clicked → Step 1 API call → Step 2 Create a new Contract with contract_notes = hello (static text). The workflow fires and creates a new row in App Data but contract_notes is always blank. Even static text does not save. Database field is type text. Screenshots attached.
Claude is guiding however we have been going around in circles - we’ve used another website Reqbin and confirmed that the API is working.
- Database ✓
- API connection ✓
- Button firing ✓
- Workflow running ✓
I’ve attached screenshots of my workflow.
And another of my database configuration:
Could you please help me understand what might be causing this?
Thank you very much!
If even a hardcoded value like “hello” is being saved as blank, then I would separate this from the Anthropic/API response first. At that point, the issue is most likely in the Bubble data/action setup rather than the API output.
I would create a completely isolated test workflow:
Button click → Create a new Contract → set only one Text field = “test”
No API step, no conditions, no custom states, no additional workflow actions.
Then check the created record directly in Data → App Data → Contracts.
If that isolated test still creates the record but leaves the field blank, I would check the following:
-
Confirm the workflow is writing to the exact same field you are checking in App Data. Your fields look very similar, so it is easy to save into one field and inspect another.
-
Confirm the target field type is actually Text. If the field is an option set, file, list, or another custom data type, Bubble may not store the value as expected.
-
Check whether any later workflow, backend workflow, database trigger, or “Make changes to thing” action is updating the same Contract record and clearing that field after creation.
-
Temporarily remove the Anthropic/API step entirely and test only the database create action with static text.
-
Only look into privacy rules if the value exists in App Data but appears blank on the page. Privacy rules usually affect what is visible, not whether the value is physically stored in the database.
Since the record is being created but the field is blank even with static text, I would focus first on wrong field selection, field type mismatch, or another workflow overwriting the newly created record.
create a workflow to catch errors with the ‘an unhandled error occured’ trigger to debug it. Your call might be throwing an error breaking the workflow.
hi Zahid, thanks so much for the guidance this fixed it. Cheers!
