From 7dcfc8baa34649e9fb7b3f790c75d1987f87b4b9 Mon Sep 17 00:00:00 2001 From: Matt Kufchak Date: Thu, 3 Jul 2025 10:06:52 -0500 Subject: [PATCH] chore: clarify trigger data limits --- content/send-notifications/triggering-workflows/api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/send-notifications/triggering-workflows/api.mdx b/content/send-notifications/triggering-workflows/api.mdx index e70337ad..6c07a11c 100644 --- a/content/send-notifications/triggering-workflows/api.mdx +++ b/content/send-notifications/triggering-workflows/api.mdx @@ -61,7 +61,7 @@ Triggering a workflow will always return a unique UUID v4 representing the workf ## Passing data to your trigger -Pass schema data required by the workflow in your `trigger` call. The payload must be a valid JSON object. There is a 1024 byte limit on the size of any single string value (with the exception of [email attachments](/integrations/email/attachments)), and a 10MB limit on the size of the full `data` payload. +Pass schema data required by the workflow in your `trigger` call. The payload must be a valid JSON object. There is a 10MB limit on the size of the full `data` payload. Any individual string value greater than 1024 bytes in length will be [truncated](/developer-tools/api-logs#log-truncation) in your logs. The workflow builder determines which data keys are required.