Why does Update or Search an item fail on the Process Instance ID?

Short answer: Map the Process Instance ID from the item's _id. After Search an item, use Data > 0 > _id from its output.

Why it happens

Update an item needs the ID of the exact item to change. If it gets the wrong value, or the action was set up before the process changed, the step fails or shows missing fields.

How to fix it

1. In an Update an item action, map the Process Instance ID from the trigger's _id. To test with one item, copy its Instance ID from the item's URL.
2. After a Search an item action, map the ID from Data > 0 > _id.
3. While testing Search an item, type a real value into the Search term to get sample output. Then swap in the mapped field.
4. Test with Use sample data, then turn on the integration.

If fields, attachments, or steps don't appear

1. Click Refresh fields in the action.
2. Make sure the process is live.
3. Remove the process from the action configuration and select it again.
4. For attachments, check that the process has an attachment field.

See the Kissflow Process connector and best practices for integrations.