Why are fields missing or wrong when mapping in a process-to-process integration?

Short answer: The integration only sees fields from the live version of the process. Click Go live, then refresh fields and retest in each integration step.

Why it happens

New or changed fields don't reach the integration until the process is live and the integration steps have been refreshed and retested. Values can also go wrong when two fields share a name, or when a formula in the target process overwrites what the integration writes.

How to fix it

1. In the source process, click Go live.
2. In the integration, open the trigger step and click Refresh fields.
3. Click Next, then Retest. New fields only show up for mapping after the retest.
4. Open each action step and click Refresh fields.
5. If a value doesn't come through, check for two fields with the same name, such as two "Manager Email" fields, and map the correct one.
6. If the target process has a formula such as _created_by.Name on a field the integration also fills, the field shows the integration's creator. Remove the formula and rely on the integration mapping.
7. Make sure the target field is editable at the steps where users need to change it. See field permissions for process steps.

For more, see using newly added fields in integrations.