Raine

it actually doesnt work. I have raised the issueto notion.

Marvin A. right. however, the agent is filling it with wrong date and time and timezone. That is what the challenge is. For example the date from the webhook is 2025-04-10T08:00:00.000Z, our goal is to format the date to be 2025-04-10T08:00:00.000+10:00 or +11 without altering the date and time just the timezone

Marvin A. here you go 🙂 https://chat.lindy.ai/aircall-to-notion-db-67b4133568f3e0395c78efc1/tasks?conversationId=67f1da9587c1133c1fe28176

sure

Marvin A. The "get the "call date" from the webhook was the recent change ive made after multiple attempts of different prompts. And yes, we are talking specifically the create notion db item.

The goal is to get the call date from the webhook trigger. The call date is in unix timestamp and it is following sydney date and time already. I have used different prompts like 1. Extract the 'Call Date' from the webhook payload (e.g., 2025-04-10T08:00:00.000Z). 2. Determine the correct Sydney timezone offset based on this date: If the date falls between the first Sunday in October and the first Sunday in April (inclusive), the offset is +11:00. Otherwise, the offset is +10:00. 3. Take the original timestamp's date and time part (e.g., 2025-04-10T08:00:00.000). 4. Replace the trailing Z with the determined offset (+10:00 or +11:00). 5. The final output should be in the format YYYY-MM-DDTHH:mm:ss.sss+HH:mm. For the example date 2025-04-10T08:00:00.000Z, the output should be 2025-04-10T08:00:00.000+10:00 because April 10th is outside the DST period. But lindy is converting the date and time instead of just changing the format and that is where the problem occurs to notion,

Marvin A. here you go https://chat.lindy.ai/aircall-to-notion-db-67b4133568f3e0395c78efc1/tasks?conversationId=67fcc87a599d4b27faaa5002

Hi Marvin A. right. I have used different prompts but lindy is changing the timestamp.