Fix
Short answer: An integration keeps a snapshot of the flow's fields from its last trigger test. Publish the flow, then refresh and retest the trigger and each action.
Why it happens
- New fields appear only after the flow is live and the trigger is retested.
- Fields that are hidden or not editable in the form and its permissions don't appear in the action.
- Changed field settings, such as a user field switched to multi-user, aren't picked up until you retest.
How to fix it
- Publish the process or board with Go live.
- Open the trigger step, click Refresh fields, then test the trigger again, or use Use sample data.
- Open each action that needs the field and click Refresh fields. Remove mappings to fields that changed.
- Search for the field by its field ID, not its display name.
These steps follow using newly added fields in integrations.
If the field still doesn't show:
- Check that the field is visible and editable in the form and its permissions, and check its visibility rule.
- Make sure the trigger uses the same flow the field lives in. A field in a dataform won't show under a process trigger.
- Reload the browser page.
- If a retest fails, check for mapped fields whose type differs between source and target, such as attachment and text. Match the types or remove the mapping.
- If nothing works, create a new integration.
Tip
To test end to end, submit a real item in the live process. A workflow simulation only lists the integrations a step would trigger.
