Skip to main content
Question

Twilio Send WhatsApp Message truncates message after Budget despite full payload in Zapier

  • June 15, 2026
  • 6 replies
  • 40 views

We are using:

Zapier -> Webhooks by Zapier (Catch Hook) -> Twilio "Send WhatsApp Message"

Problem:

The WhatsApp message is being truncated after the "Budget" field.

Expected message:

- Part
- Category
- Classification
- Brand
- Engine
- Year
- Budget
- Condition
- Urgency
- Part Number
- City
- Buyer Message

What we verified:

1. The webhook receives the full payload.
2. Zapier Step 3 is configured with the full message.
3. Run Details -> Data In contains:
   - Condition
   - Urgency
   - Part Number
   - all remaining fields.
4. Twilio returns HTTP 201 Created.
5. WhatsApp receives only the first part of the message.
6. The test message is under 300 characters.
7. The truncation always occurs around the Budget field.
8. We tested with short values such as:
   - Engine: 999
   - Year: 1999
   - Budget: 999
   - Part Number: ABC123

Evidence:

Run Details shows the complete message including:
Condition: Cualquiera de las anteriores
Urgencia: high
Forja / núm. de parte: ABC123

But the WhatsApp message received ends around:
Budget: 999

Question:

Has anyone seen the Twilio "Send WhatsApp Message" action truncate messages even when:

- Zapier receives the full payload,
- Twilio returns HTTP 201,
- and the message is far below 1024 characters?

Is this a known limitation, bug, or configuration issue?

We are using:

Zapier -> Webhooks by Zapier (Catch Hook) -> Twilio "Send WhatsApp Message"

Problem:

The WhatsApp message is being truncated after the "Budget" field.

Expected message:

- Part
- Category
- Classification
- Brand
- Engine
- Year
- Budget
- Condition
- Urgency
- Part Number
- City
- Buyer Message

What we verified:

1. The webhook receives the full payload.
2. Zapier Step 3 is configured with the full message.
3. Run Details -> Data In contains:
   - Condition
   - Urgency
   - Part Number
   - all remaining fields.
4. Twilio returns HTTP 201 Created.
5. WhatsApp receives only the first part of the message.
6. The test message is under 300 characters.
7. The truncation always occurs around the Budget field.
8. We tested with short values such as:
   - Engine: 999
   - Year: 1999
   - Budget: 999
   - Part Number: ABC123

Evidence:

Run Details shows the complete message including:
Condition: Cualquiera de las anteriores
Urgencia: high
Forja / núm. de parte: ABC123

But the WhatsApp message received ends around:
Budget: 999

Question:

Has anyone seen the Twilio "Send WhatsApp Message" action truncate messages even when:

- Zapier receives the full payload,
- Twilio returns HTTP 201,
- and the message is far below 1024 characters?

Is this a known limitation, bug, or configuration issue?

6 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • June 15, 2026

Hi ​@Cuauhtemoc 

Help links for using WhatsApp in Zaps: https://zapier.com/apps/whatsapp-notifications/integrations#help

NOTE: Messages are limited to prefilled templates for:

  • New Lead
  • New Message
  • Payment Confirmation
  • New Order
  • Shipping Confirmation
  • Calendar Reminder
  • Zap Error

 

For us to have more context, post screenshots showing how your Zap steps are outlined and configured in the CONFIGURE tab while in EDIT mode with the field mappings visible.


  • Author
  • New
  • June 15, 2026

Hi Troy,

Thanks for your reply.

Just to clarify, this Zap is not using the WhatsApp or WhatsApp Notifications app.

Step 3 is:

Twilio → Send WhatsApp Message

The Zap flow is:

Webhooks by Zapier → Custom Request → Twilio Send WhatsApp Message

The full message is present in Step 3 Data In, including Condition, Urgency and Part Number.

However, the Data Out and the WhatsApp message received are truncated after Budget.

Do you know of any limitation or known issue specifically with the Twilio "Send WhatsApp Message" action?

Thank you.


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • June 15, 2026

@Cuauhtemoc 

Help links for using Twilio in Zaps: https://zapier.com/apps/twilio/integrations#help

 

My message has been cut short!

Twilio allows for sending of up to 1600 characters but the Twilio app will automatically truncate messages down to 160 characters. You’ll want to make sure that the "send large message" option is set to “yes” on the Zap to ensure the full message is sent.


  • Author
  • New
  • June 15, 2026

Thanks Troy.

That is very helpful.

The issue is that we cannot find the "Send Large Message" option anywhere in the Twilio → Send WhatsApp Message action.

We reviewed the Zap configuration, the run details, and even the underlying configuration, but we cannot find a field called "Send Large Message".

Could you tell us exactly where that option is located for the Twilio Send WhatsApp Message action?

A screenshot or navigation path would be greatly appreciated.

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • June 15, 2026

@Cuauhtemoc 

The character limit may be hardcoded in the backend of the Twilio Zap action.

You can try opening a ticket with Zapier Support to get official confirmation: https://zapier.com/app/get-help

Or you can try using this Zap action to send WhatsApp messages via Twilio: Twilio - API Request


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • June 23, 2026

Hey ​@Cuauhtemoc 👋

I checked and the “Send Large Messages” option is only available for Twilio’s Send SMS action, not the Send WhatsApp Message action. There’s an existing bug report for this which was mentioned in this related Community topic over here:

I’ve gone ahead and added you to the list of folks being affected by that 160 character limit. I can’t give any sort of estimate as to when it will be fixed by, but we’ll notify you by email as soon as it is.

The workaround would be to try sending the message using a Twilio API Request action like Troy suggested. Have you had a chance to give that a try yet?

Let us know how it goes when you do!