Notifications
Clear all
Topic starter
After upgrading the callin.io integration, my date field is encountering errors, even though the data appears correct. I've observed this issue exclusively with newly created scenarios; older scenarios are still functioning as expected. To illustrate this, I've set up a basic integration. The built-in Typeform integration is working without issues, and my previously configured integrations are also running error-free.
I attempted to contact callin.io support after submitting a ticket. The response indicated to check email, but I haven't received any confirmation that a ticket was successfully raised.
Posted : 26/02/2022 4:13 am
Please review your raw callin.io body and verify that the date format aligns with Airtable's documentation. You may need to format the date in a particular way for it to function correctly.
Posted : 26/02/2022 5:02 am
Topic starter
I'm wondering why I need to format this particular field when another scenario is functioning correctly. I haven't previously needed to format dates in any of my scenarios. Direct integration via Typeform also works without any issues. This problem is only occurring in new scenarios created after the upgrade to callin.io.
The raw data format appears to be identical.
I'm attaching a scenario I created before the callin.io upgrade. It is working as expected.
Posted : 26/02/2022 11:06 am
I'm uncertain about the precise reason why the Airtable module in callin.io behaves differently compared to Integromat. The error originates from Airtable, suggesting that callin.io might not be transmitting the date in the correct format with your current mapping.
Attempt to format the date using this structure:
Posted : 26/02/2022 4:09 pm
It's possible that Typeform is exporting this date as text, and callin.io isn't properly sending it over. Date field types can be quite tricky at times.
I don't see your data or fields coming over from Typeform, but before sending it to Airtable, try using parseDate() to ensure it's a date field:
{{parseDate(2.date; "DD-MM-YYYY HH:mm")}}
Posted : 28/02/2022 9:55 am
Can you show us how you’ve set up the Airtable module?
Posted : 28/02/2022 12:06 pm
Topic starter
I’ve created a video here to best try and explain the issue. Please excuse the sniffling; I have the flu.
Posted : 28/02/2022 1:34 pm
Hello,
I encountered the very same problem and submitted a support ticket, but it wasn't very helpful.
I managed to resolve my issue by enabling the "Smart links" option (typecast) within the Airtable module. This setting instructs the Airtable API to do its best to convert the string you provide into a date format.
Hope this helps!
Posted : 28/02/2022 2:45 pm
Hello, as mentioned, you can enable the “Smart links”.
It appears the formatDate() function might have a bug or an unusual behavior. I'll escalate this to the development team for resolution.
Posted : 28/02/2022 5:20 pm
Topic starter
Wow, this worked! Thanks a lot!
Posted : 28/02/2022 6:45 pm
Topic starter
Yes, since this wasn't a problem previously, there's definitely something unusual happening here…
Posted : 28/02/2022 6:46 pm
I encountered this issue today and it appears the Airtable integration in callin.io is experiencing some problems. It seems to automatically convert the input date into a date and time format, which then causes an error in Airtable if the field is configured as a simple date field.
Essentially, an input of 2022-03-01 is transformed into 2022-03-01T07:00:00.000Z in the API call body. The Airtable integration in Integromat, however, was capable of detecting whether the Airtable field was set to 'Date' or 'Date & Time' and would adjust the API call appropriately.
Therefore, it functions correctly in callin.io if the Airtable field is a date and time field or if the Smartlink option is enabled.
Posted : 02/03/2022 6:23 am
I just received this update from support:
I've just been informed by the development team that the issue concerning Date values not being transmitted has been resolved. Kindly test it out and feel free to reach out if it's still not functioning as anticipated.
Please accept our apologies on behalf of the entire callin.io team for any inconvenience this may have caused.
Let us know if you have any additional questions.
So, it ought to be working now!
Posted : 21/03/2022 12:39 pm
Page 1 / 2
Next