Auto-Crosspost from Telegram Channel to Facebook Page via Make.com

Hi everyone,

I’m working on a scenario where I post photos on my public Telegram channel, and I want to automatically publish the same post (photo + caption) to my Facebook Page using Make com.

The flow works like this:

  1. Telegram Bot – Watch updates

  2. HTTP – Get file info from channel_post.photo[3].file_id

  3. HTTP – Get a file using the file_path from step 2

  4. Facebook Pages – Create a photo post

The issue is:

  • Even when I get the last and largest photo variant (e.g., 960x1280) using last(photo).file_id,

  • The downloaded file from Telegram is very small in file size (e.g., 100–200 KB or less),

  • Facebook throws an error:
    Error 324 - Missing or invalid image file (OAuthException)

I verified that the image looks fine in Telegram, and I receive the correct file_path from the API. But the photo is clearly compressed, and Facebook refuses to accept it due to small size or corruption.

❓ My question:

✅ Is there a reliable way to get the original uncompressed image from a Telegram channel post?
Or does Telegram always compress photos posted in channels?

Any idea how I can send a proper high-quality image to Facebook from Telegram using Make com?

Thanks in advance 🙏

Welcome to the Make community!

We’d love to help, however, you have not provided sufficient information to demonstrate the problem that would allow us to reproduce the scenario and any issue/s and/or error/s.

To allow others to assist you with your scenario, please provide the following:

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are extremely important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

  • the full scenario,
  • any error messages,
  • individual module fields,
  • relevant filter settings (conditions), and
  • each module’s output bundles
  • any external services (spreadsheet headers, sample data, regex101.com, etc.)

2. Scenario Blueprint

Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!

To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.

3. Module Output Bundles

Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).

Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.

You can upload the file here by clicking on this button:

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.

To provide code/text using Markdown format, you can type a code fence.
Add three backticks ``` in a separate line before and after the content, like this,

```
text goes here
```

Alternatively, you can upload your file and share the public link** —
(this method is only recommended for large files exceeding the forum upload limit)

Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.

Sharing these details will make it easier for others to assist you.

I set up a Telegram-to-Facebook crosspost flow in Make.com using the Telegram “Watch Messages” module and Facebook “Create a Post” action. Key part was formatting the message to strip out unwanted elements and handling media types separately. Also make sure you’ve got the right Facebook Page permissions connected. Once it’s live, it runs smoothly and saves a ton of time.