Skip to main content
Solved

Details regarding Make modules send text and send message

  • March 2, 2026
  • 3 comments
  • 22 views
KlickTipp_ricardo

I receive errors when trying to send out messages using the Manychat Make modules for “Send text” and “Send message”

 



 


Could someone shed some light on what they intended for? I am planning to collect leads via Instagram and Telegram and to then send out Texts/Messages via the according channel where the contact came from. However the errors claim there was no prior contact and no message can be sent and also mentions message Tags:

[400] Content can’t be sent to the subscriber without a message tag. Subscriber’s last interaction was over 70h ago (more than 24 hours ago)

When adding a Tag I receive:

[400] Validation error: Message tags are no longer supported for Facebook Messenger.

This leads me to believe that those modules are supposed to be used for Facebook Messenger and not Telegram and Instagram. Is that correct?

I assumed you can use the modules “send text/message” for any of the channels and that the subscriber ID would carry the attached channel so that Manychat know via which channel to send the message. Is this wrong and will Manychat always try to send out via Facebook in that case?

Interestingly if I only apply a Tag and then use an automation within Manychat to send out a message the Telegram and Instagram message arrives as expected.

I would highly appreciate any hint on this issue.

Best answer by Gustavo Boregio

Perfect, to do that you’ll need to use Manychat’s API since the ‘Send Messages’ only works for Messenger.

Here’s the documentation: https://api.manychat.com > you’ll want to use the sendContent or sendFlow endpoints.

    3 replies

    Gustavo Boregio
    Forum|alt.badge.img+7
    • Gustavo Boregio
    • Community Moderator & Expert
    • March 4, 2026

    ​@KlickTipp_ricardo Can you explain your full setup?

    And what channel are you using (Instagram, WhatsApp, Messenger)?

    These actions can only be used with existing subscribers in Manychat (you need to have their Manychat user ID).

    And Message Tags were deprecated last month, so you can’t use them anymore to send messages outside the 24 hours…

    The only viable way to send messages outside the 24 hours is with WhatsApp - but to do it you need to use the Send Flow or Manychat’s API.

    🧑‍💻 https://engimarketers.com | 📲 https://superarmeonline.com
    KlickTipp_ricardo

    ​@Gustavo Boregio 
    Thank you very much for reaching out.

    I am using the channels Instagram and Telegram. 

    In Manychat I set two automations up that if a user sends me a message I am asking for more information. Once that information arrived I sync the contacts to a email marketing tool (including the Manychat subscriber ID) via Make which works without any issue.

     

     


    From that email marketing tool I am then sending out an API call to a Make scenario and I pass the message I want to sent and the subscriber ID from Manychat. When using the modules in make as described then I am receiving the mentioned errors.
     


    I start to believe that if you have users in Instagram and Telegram start interacting with you that the generated/collected subscriber IDs from Manychat can not be user for the Make modules send text and send message. Could it be that they are supposed to be used for facebook messenger or another channel?

    In both instagram and telegram I have fresh test users that interact and trigger the automations as expected but once I use the send text or message module I receive errors even though I am way below the 24h limit.

    Gustavo Boregio
    Forum|alt.badge.img+7
    • Gustavo Boregio
    • Community Moderator & Expert
    • Answer
    • March 4, 2026

    Perfect, to do that you’ll need to use Manychat’s API since the ‘Send Messages’ only works for Messenger.

    Here’s the documentation: https://api.manychat.com > you’ll want to use the sendContent or sendFlow endpoints.

    🧑‍💻 https://engimarketers.com | 📲 https://superarmeonline.com
    Community Terms & ConditionsCookie settingsAccessibility statement