JSON Payload won't update

What I am trying to do:

  1. I have a table called “NEEDS APPROVED.”
  2. I have a table called “MAIN DATA.”
  3. I don’t want data submitted directly into the MAIN DATA table, just in case there are errors or inappropriate content, so I am using a buffer table, aka NEEDS APPROVED.
  4. When the Boolean field (APPROVE) is checked, the data will appear in the APPROVED VIEW.
  5. When the item enters the APPROVED VIEW, a new row with the relevant data should be created in the MAIN DATA table.

I set up an HTTP request in the automation, copied the webhook URL from the automation, and created the webhook in the NEEDS APPROVED table. I selected “Let me select individual events.”

I can test the trigger, and it worked, pulling the data into the JSON Payload. When I went to map everything, the automation was giving me an error in the multiselect fields because the items didn’t match. I had forgotten to change the NEEDS APPROVED table after changing the options in the MAIN TABLE, so I went back and did that. I then retested the HTTP Request part, but no matter what I do, the selection value is stuck on the old select name. I refreshed pages, turned the automation off and on again, but it is still showing the old value in the JSON Payload.

On another note, when mapping Multiselect fields from one table to another, how does the field mapping work? Sometimes the field will only have one item, and sometimes multiple.

I tried to get this to work using Make.com as well with no luck, though I would rather use Baserow’s internal things if possible because I figured it would be more compatible….

Field types I need to map from the NEEDS APPROVED table to the MAIN DATA table:

  • Multiselect
  • Single Select
  • Linked Field
  • File Field

PS: The automation randomly says it doesn’t exist and wants to take me back to the dashboard.

Hey @Iokaar

I’m wondering, are you using the webhook for a specific reason? Because with what you describe my first try would be with a rows updated trigger that wait for rows update in theNEEDS APPROVED table then an iterator node to iterate over the rows and for each row I would use a router node with a condition on the Approved field. If true then we use a Create a row node to create the row in the main table then we delete it from the NEEDS APPROVED table.

Something like

May be it doesn’t solve all your issues yet but let me know what you think.