I have a 3 step ZapListen to a request and intercept the details Obtain epoch date/time from one of the attributed in step 1 Add a date formatter to convert epoch time from step 2 to ISO8601 format. This saves it to param called output Pass that date to a custom PATCH request in json body that posts to another endpoint ex: {started_at:”<output>”)Actual results : It appears to pass exactly the same date/time ISO combination . Any additional configuration needed so that json body receives latest date/time and is dynamic

Question

Date format step seems to hardcode date/time

3 months ago
30 May 2024
3 replies
21 views

I have a 3 step Zap

Listen to a request and intercept the details
Obtain epoch date/time from one of the attributed in step 1
Add a date formatter to convert epoch time from step 2 to ISO8601 format. This saves it to param called output
Pass that date to a custom PATCH request in json body that posts to another endpoint ex: {started_at:”<output>”)

Actual results : It appears to pass exactly the same date/time ISO combination . Any additional configuration needed so that json body receives latest date/time and is dynamic

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.