Workflow

Test the first request before configuring the second. Zapier can only offer output fields that exist in the selected test record. Then insert the first request’s field as a mapped token rather than typing its sample value.

Test setup

We created a private draft Zap with three steps:

  1. Schedule by Zapier — Every Day.
  2. Webhooks by Zapier GET https://jsonplaceholder.typicode.com/posts/1.
  3. Webhooks by Zapier GET https://jsonplaceholder.typicode.com/users/{userId} where {userId} was mapped from step 2.

The data came from JSONPlaceholder’s synthetic public API. The Zap was not published or turned on.

Tested steps

  1. Add and test the first GET request.
  2. Confirm the response exposes userId.
  3. Configure the second GET URL with static text through /users/, then insert the userId field from step 2.
  4. Test the second request.
  5. Repeat the second-step test after checking the mapping.

The first request returned post data including userId: 1. The second request used that mapped value and returned the matching synthetic user object. Zapier’s test log showed multiple successful tests of the final GET while the workflow remained a draft.

Common failure mode

If the mapped field is missing, retest the first request and select a record that actually contains it. Zapier’s documentation notes that only static values and mapped fields are transferred, and a mapping with no test data can leave the later action blank.

URL construction

Keep the fixed portion of the endpoint as text and insert only the changing field as a Zapier mapping token. Do not paste a rendered sample such as 1 if the value must change on future runs.