Lindy Timestamp Issue: Incorrect Conversion from Aircall to Notion | Lindy Community

Lindy Timestamp Issue: Incorrect Conversion from Aircall to Notion

Hello everyone. I just wanted to know if you are experiencing this kind of scenario too? Lindy is incorrectly converting the call timestamp from Aircall. The Unix timestamp is already in Sydney time, but Lindy treats it as UTC, applies the Sydney offset again, and sends the wrong time to Notion. This results in incorrect dates showing up. Is there a way for Lindy to not convert the timestamp, but simply append the correct Sydney offset (+10 or +11) to the existing time?

👀1

18 comments

Marvin A.
·
·
hmm not sure how your Lindy is set up, but sounds like this should be solvable with a clear prompt for the agent
Raine
·
·
Hi Marvin A. right. I have used different prompts but lindy is changing the timestamp.
Marvin A.
·
·
can you share a task url of where this happened?
Marvin A.
·
·
How to share your Lindy task URL: 1. Click your Lindy agent → click “tasks” 2. Find the task you need help with 3. Click the specific task (you should see the full execution) 4. Copy that page URL from your browser 5. Paste the URL in your support request Note: The URL should include “conversationID” followed by a number 💡 Screenshots are also helpful!
Raine
·
·
Marvin A. here you go https://chat.lindy.ai/aircall-to-notion-db-67b4133568f3e0395c78efc1/tasks?conversationId=67fcc87a599d4b27faaa5002
👀1
Raine
·
·
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.
·
·
and we are talking specifically about the Create Database Item notion step?
Marvin A.
·
·
From what I see in the task the prompt for the field was “get the “Call Date” from the webhook”.👀 Or am I missing something
Raine
·
·
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.
Marvin A.
·
·
okay! can you share the task url where you prompted it to format the date correctly and it failed to do so?
Raine
·
·
sure
Raine
·
·
Marvin A. here you go 🙂 https://chat.lindy.ai/aircall-to-notion-db-67b4133568f3e0395c78efc1/tasks?conversationId=67f1da9587c1133c1fe28176
👀1
Marvin A.
·
·
Hm I see the same for this task: get the "Call Date" from the Webhook Since the field is called Call Date + the notion prop is a date field → the agent will go ahead and try to fill that accordingly
Raine
·
·
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.
·
·
The notin database item prop is defined as date field → only accepts date formats. You can tell the LLM to add 10 or 11h to the datetime but not change the format in this case if that makes sense
Marvin A.
·
·
or maybe you can if you change it from UTC to ISO 8601
Marvin A.
·
·
🤔
Raine
·
·
it actually doesnt work. I have raised the issueto notion.