Telegram to Facebook Page: posts are not being published

Questions
,
1

:bullseye: What is your goal?

Hi everyone,
I’m trying to build a Make scenario that automatically copies posts from a Telegram channel to a Facebook Page.
The goal is to support different types of Telegram posts:

  • Text-only posts
  • Image + caption

For example, if I publish this in my Telegram channel: “New product available today!” with an image attached, I want Make to automatically publish the same image and caption on my Facebook Page.

For a text-only Telegram post, I want the text to be published as a normal Facebook Page post.

:thinking: What is the problem & what have you tried?

My scenario currently starts with:

  • Telegram Bot → Watch Updates

The Telegram bot is already created and added to my Telegram channel.

Then I added a Router with different routes for different types of content.

For the text route, I created a filter using:

  • Channel post → Text → Exists

Then I added:

  • Facebook Pages → Create a Post
    and mapped:
  • Channel post → Text
    to the Facebook post message.

For the image route, I added a filter for the image/photo. Then I added:

  • Telegram Bot → Download a File
    The idea is to take the Telegram image’s File ID, download the actual file, and then pass it to:
  • Facebook Pages → Create a Post with Photos
    I also mapped the Telegram:
  • Channel post → Caption
    to the Facebook post message.

:clipboard: Error messages or input/output bundles

I attached a pdf with screenshots of the simple and advanced error logs

:link: Create public scenario page

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

2 error.pdf (995 KB)

4

Your scenario design is close to right, so this is probably one of the following rather than a rebuild. Roughly in order of how often each is the cause:

  1. Channel posts may not be arriving at all. Telegram only delivers channel_post updates to a bot that is an ADMINISTRATOR of the channel - being added as a member is not enough. Also, in Watch Updates, if the Update types field is left at its default, channel_post is often not in the subscribed list, so the scenario never runs. Set Update types to explicitly include Channel post, then post in the channel and check whether module 1 produces a bundle at all. If it does not, nothing downstream is broken - the trigger simply is not subscribed.
  2. The photo field is an array, not a single value. A Telegram photo arrives in several sizes. If you mapped Channel post > Photo > File ID without picking an element, you get either nothing or the tiny thumbnail. Map the LAST item of that array (the largest size), then pass that file ID to Download a File.
  3. Download a File returns binary, and Create a Post with Photos wants that binary. Map the whole file from Download a File (data plus file name) into the photo field - not the file ID, and not a URL. If the Facebook module reports an empty or missing data value, this is almost certainly it.
  4. Facebook permissions. Publishing to a Page needs pages_manage_posts and pages_read_engagement on a token for a Page you actually administer. If the error mentions (#200) or insufficient permission, reconnect the Facebook Pages connection, grant both scopes and select the right Page. A personal-profile connection will never publish to a Page.
  5. Albums will duplicate. Several images posted at once arrive as separate updates sharing a media_group_id, so you get one Facebook post per image. If that matters, group on media_group_id before publishing.

For what it is worth, the parts you described are correct: Channel post > Text > Exists is the right filter for text-only posts, and using Caption rather than Text on the image route is right, since a photo post carries a caption and no text.

If you paste the actual red error text from the two failing modules (as text, not a screenshot), I can tell you which of the five it is instead of guessing.