Hi everyone,
I’m reporting a blocking issue with the Alegra – Create Invoice action in Zapier.
Issue
The date and dueDate fields are treated as datetime fields by Zapier.
Even when providing a correctly formatted value (YYYY-MM-DD), Zapier internally sends a datetime value with timezone, for example:
2025-12-11T00:00:00-06:00
Alegra’s API expects date-only values and rejects datetimes with the error:
“The value 2025-12-11T00:00:00-06:00 is not valid for a date field in Y-m-d format”
As a result, the invoice cannot be created.
⸻
What has been tested
• Formatter by Zapier (Date/Time → Format)
• Text formatting and Replace
• Static dates and manual input
• UTC timezone
• Passing pre-formatted YYYY-MM-DD strings
In all cases, Zapier still sends a datetime value instead of a plain date.
⸻
API reference
Alegra’s API documentation specifies that invoice dates must be sent as date-only strings:
POST /api/v1/invoices
{
"date": "YYYY-MM-DD",
"dueDate": "YYYY-MM-DD"
}
Docs:
https://developer.alegra.com/api-reference/invoices/create-invoice/
Calling the same endpoint via Webhooks by Zapier with these values works correctly, confirming this is a limitation of the Alegra Zapier connector.
⸻
Expected behavior
• Allow sending date and dueDate as plain strings
or
• Provide a custom/raw input mode for these fields
⸻
Workaround
Use Webhooks by Zapier to call the Alegra API directly.
This workaround works, but the official Alegra app remains unusable for invoice creation.
⸻
Thanks in advance — hoping this helps get the connector fixed.
Best regards,
Anxapz
