Why does Create an item force me to fill required, calculated or hidden fields?

Short answer: The create action asks for every field marked required, even computed or conditionally shown ones. Remove the required setting where it doesn't belong, refresh the action, and keep the fields you map editable at the first step.

Why it happens

• The action reads the required setting, not the field's visibility, so a conditionally required field counts as required.
• Computed fields are read-only, so you can't supply a value for them.
• Values you send on create or submit go into the start step. Fields that are hidden or read-only there may not accept them.

How to fix it

If a computed field is marked required:

1. Remove the required setting from the computed field and publish the process.
2. In the integration, open the action and click Refresh fields.

If a conditionally required field, such as an attachment, blocks the action:

1. Set the field to not required in the process and publish.
2. In the action, click Refresh fields, leave the field empty, and continue.
3. Refresh the fields again.
4. Set the field back to required in the process and publish.

If values don't save:

1. Open the process editor and go to Permissions.
2. Select the Start step and make each field you map Editable. If the field sits in a hidden or read-only section, make the section editable too: section permissions override field permissions. See field permissions.
3. Refresh and retest the action.