I’m getting the following error:
error: “Field ‘{name}’ is required”
However, there is no “name” field in my database.
Please check this issue.
@Headchef.Yang Hi there! 
Thanks for reaching out and providing the screenshots. I actually took a closer look at your second screenshot, and it seems there is already a “name” field located at the very right end of your columns. The system might be conflicting with it. Could you try deleting that specific “name” column and giving it another shot? Let me know if that resolves the issue for you!
The “name” field was a field I temporarily created for testing when the error occurred, but it has already been deleted. However, the same error is still occurring.
Please check this again.
Also, this “name” field was set to not required.
Right now this field has been deleted, but the same error is still occurring.
@Headchef.Yang Understood. Since the field is deleted but the error remains, this looks like a deeper issue where a certain node or integration is strictly requiring a name payload under the hood. I have forwarded your detailed screenshots and this case to our technical team for further investigation. We will get back to you as soon as we find the root cause!
@Headchef.Yang Hello! We found the root cause. This error happens because a mandatory field is missing in your “Create record” action setup. The error message incorrectly says “name” instead of the actual field’s name due to a known UI bug (which our team is currently fixing!).
To resolve this right now, please manually check your datasheet to identify which fields are set to “Required”, and make sure they are included and mapped in your action configuration. Let us know if it works after adding the required field!
@Headchef.Yang Just a quick update: this is fixed! 
Turns out there was some old hardcoded validation acting up. We’ve merged the patch to get rid of it.
Try deleting that field again and let us know if you hit any more snags. Cheers!