Send Telegram Stars Back to the Source After Forwarding

You can forward a Telegram channel’s post to your readers and send paid Stars back to the original post afterward. RedFox Auto Forward Telegram’s Paid Reaction add-on has a source_only setting for exactly that choice: once the task successfully forwards a message, the add-on attempts the configured Star reaction on its source message instead of the copy.

For a publisher sharing a creator’s work with permission, this turns a separate “go back and thank the source” action into part of the forwarding workflow. The useful outcome is support for the originating channel—not a promise of extra views, audience growth or independent reader endorsement.

This guide covers RedFox Auto Forward Telegram (@AutoForwardNew_Bot). RedFox develops the product; Auto-Bot.io publishes this guide. The settings below follow the official Paid Reaction documentation checked November 6, 2026.

Support the original, not automatically the copy

Telegram’s Star Reactions announcement describes Stars as a way to support channels and content creators. Its current reactions documentation explains the mechanism: a paid reaction transfers the selected number of Telegram Stars to the channel’s balance.

That makes the reaction’s location important. Supporting a source post and reacting to your own forwarded copy are different spending decisions. RedFox documents three scopes:

• Support the original: source_only. The reaction goes to the original source message. Choose this when you want to support the channel whose post you reused.
• React to the copy: target_only. The reaction goes to the forwarded message. This is the documented default; use it when you deliberately want support on the receiving channel’s copy.
• Support both locations: both. RedFox reacts to the source first, then the target. Choose this only when both locations are eligible and you intend to fund both charges.

For the creator-support workflow, select source_only explicitly. Leaving the default untouched points the reaction at the target. Do not assume the add-on recognizes which channel you intended to support from the wording of a forwarded post.

Start with a source channel that supports paid reactions. Telegram documents paid reactions on channel posts and says channel administrators must enable them. Do not extend that statement to every group, private chat or forwarded destination. Your source account also needs access, and you need permission to redistribute the content; sending Stars is not a content licence.

Write one source-support policy before enabling spending

Consider a regional arts bulletin that has permission to share selected posts from an independent illustrator’s channel. The editor wants the bulletin’s subscribers to see the work, while the original channel receives a small thank-you when a selected post is successfully forwarded.

A useful operating policy is:

One approved creator channel, one bulletin destination, one forwarding task. Send 2 Stars to the original post after a successful forward. Do not react to the bulletin’s copy. Review the first 12 qualifying source posts before continuing.

This is a worked planning example, not a product preset. It deliberately uses one target so that source-post counts and destination-copy counts are easy to reconcile. Before expanding to several targets, confirm how your actual task counts reactions; the feature guide does not define multi-target charging in detail.

• Which source? Record the exact channel, not just a similar display name.
• Which posts? Keep the task’s existing selection rules explicit. Paid Reaction applies to messages processed by that task, not an independent list of favourite posts.
• Who may spend? Give one operator responsibility for the Stars balance and the decision to continue.
• Where should support appear? Source only, with an intentional privacy choice.
• When will you review? Choose a small, finite checkpoint you can supervise. Do not mistake that checkpoint for an automatic product spending cap.

If the source is a private or Protect Content channel, RedFox’s built-in protected-content forwarding addresses the forwarding capability. Paid reactions remain a separate eligibility and spending decision: protection status alone does not establish that a particular source accepts Stars.

Separate add-on access from the Stars you send

There are two costs to understand before starting:

1. Access to the RedFox add-on. The Add-ons guide describes credit-based, time-limited access. Open Menu → My Addons, find Paid Reaction and check whether it is already active. Review the actual price, duration and any renewal choice before purchasing; do not reuse an old sale price.
2. Telegram Stars spent by the reactions. RedFox says Paid Reaction requires a sufficient Telegram Stars balance. Unlocking the add-on is not a Stars top-up, and a RedFox credit balance is not a Telegram Stars balance.

The feature allows a configured amount from 1 to 5 Stars. In the example, 12 successful source-only reactions at 2 Stars each would spend 24 Stars. That is an illustrative reaction budget, not a daily limit enforced by the add-on, a dollar conversion or a prediction that every attempt will succeed.

Keep the number of enabled tasks in the same budget review. RedFox’s once-only rule is per message per task; it does not establish a shared spending cap across two tasks that process the same source. Avoid overlapping paid-reaction routes unless their combined spending is deliberate.

For the broader distinction between subscription access, credits and individual extensions, use the Credits and Add-ons guide. None of those balances proves that a reaction was sent.

Configure the task around the source-support decision

Use the official Web app or the official mobile app to inspect the exact forwarding task. Keep Paid Reaction disabled while you check the route and ordinary delivery. If creating a new task, select a quiet source and private destination you control first: the task-creation guide says a newly created task is activated.

1. Confirm source, target and selection rules. Verify which source posts can enter this task and check that the intended copy arrives without Paid Reaction. If you still need the basic route, follow the forwarding setup guide rather than adding a spending action to an unexplained delivery problem.
2. Check source eligibility in Telegram. For a channel you own, Telegram’s documented path is Channel Settings → Reactions → Enable Paid Reactions. For someone else’s channel, confirm that the relevant posts accept paid reactions; ask the channel owner if needed. Do not change another creator’s settings.
3. Review Paid Reaction access. Confirm the add-on’s current access period and the available Stars balance. Purchase or top up only if you actually intend that cost.
4. Set the reaction scope to source_only. Choose the desired amount within the documented 1–5 range. For this example, choose 2.
5. Choose privacy deliberately. RedFox’s anonymous mode makes the reaction anonymous; default uses the Telegram account’s privacy settings. Default does not mean anonymous.
6. Save and read back the task’s values. Confirm the selected scope, amount and privacy before enabling Paid Reaction for the controlled check. Do not enable it on unrelated tasks.

Telegram’s public API supports additional reaction identities, including sending on behalf of a channel. That does not establish an equivalent selector in RedFox’s add-on. Use the privacy choices RedFox actually documents instead of assuming every Telegram API option appears in the product.

Check a forward and its reaction as two separate outcomes

A successful forward triggers the add-on; it is not proof that the paid reaction succeeded. RedFox says each message receives only one paid reaction per task and that failed reactions are not retried. Use a controlled check before relying on the workflow for a real creator channel.

Choose an isolated channel you control with paid reactions enabled and a private receiving destination. Use harmless original content, one route and a Stars amount you explicitly authorize. With the task stopped or its reaction action disabled, prepare the source, confirm no other task can spend on the same specimens, and record the balance and existing reactions before enabling the action.

1. Check a new qualifying post. Inspect the matching destination copy, the original source post’s paid reaction and your account’s Stars activity. Record whether this specific delivery and source-support action occurred.
2. Check a harmless excluded post, if your task already has a selection rule. Confirm there is no destination copy and no spending attributable to this task for that post. Keep other paid-reaction tasks out of the check so that their spending cannot obscure the selection boundary.
3. Inspect the receiving copy too. With source_only selected, check that this task did not add a paid reaction to the target. The intended result is support on the original, not on the default target location.

If no exclusion rule is part of your workflow, do not invent one just to complete the second check. Review the actual selection policy instead. If a reaction’s attribution is unclear because other people are reacting, a larger visible counter alone is inconclusive; compare the controlled baseline with your account’s own activity.

Stop after the planned specimen and reconcile the result before continuing. Do not deliberately drain the balance, break forwarding permissions or send a second paid reaction just to simulate a failure. An ordinary copy without a reaction can remain a valid forwarded post; record the missing support action separately.

Run a support workflow, not an engagement scoreboard

Once the controlled check agrees with the policy, enable Paid Reaction only on the intended live task in a quiet window. Recheck the real source, destination, source-only scope, amount and privacy. Watch the first qualifying post, then review actual Stars activity at the checkpoint you chose.

Keep a short private handoff note:

Task: arts_bulletin
Approved source: exact creator channel
Destination: exact bulletin channel
Reaction scope: source_only
Amount: 2 Stars
Privacy: anonymous or default — record the chosen value
Review checkpoint: first 12 qualifying source posts
Observed: forwards, confirmed reactions, actual Stars spent
Next decision: continue, reduce scope or disable Paid Reaction

The record should count actual spending, not simply multiply every forwarded message by the configured amount. A failed reaction, an ineligible post or an overlapping task can make those totals differ. For an unresolved mismatch, preserve the task, source-post reference, delivery result, configured amount and non-secret Stars activity for RedFox support. Never send login codes, passwords, tokens or session files.

If a reaction fails, do not recreate the task, replay the source feed or run a history Clone to force another charge. The documentation’s no-retry rule means the support action needs its own reconciliation. Any manual follow-up is a new spending decision; establish whether a charge already occurred first.

Paid Stars are your contribution, not votes from your subscribers. Do not present automated support as organic audience enthusiasm or expect it to purchase redistribution rights. The clean promise to the creator is simpler: your chosen source posts can receive a small, explicit contribution after your task successfully forwards them.

Questions before you enable Paid Reaction

Does this unlock paid photos or videos?

No. Paid Reaction sends Stars as a reaction after successful forwarding. Unlocking paid media is a different operation covered by Paid Media Auto-Purchase. Neither payment itself grants permission to republish someone else’s content.

Will the add-on retry a failed Star reaction?

The current RedFox feature guide says it will not. Check the forwarded copy and the payment outcome separately rather than treating a reaction failure as a reason to resend the post.

Will enabling it reward every older source post?

The documentation says it applies only to messages processed by the task and runs after successful forwarding. Enabling it is not a documented command to reward an entire existing archive. Keep this guide’s new-post workflow separate from history cloning.

Does once per message mean my whole account cannot spend twice?

No. RedFox states the rule per message per task. Keep overlapping tasks, manual reactions and other spending in your budget review. Do not infer account-wide deduplication or a daily cap from that rule.

Make source support part of the publishing decision

Explore RedFox Auto Forward Telegram, then review Paid Reaction for one approved creator channel. Begin with the intended recipient, an explicit Stars amount and a controlled source-only check—not a default reaction on every receiving copy.

Choose the Web app, iOS app or Android app, whichever suits you. Web and mobile apps offer fuller management than the limited Telegram-bot entrypoint. Active tasks run in RedFox’s cloud without keeping the interface open, so closing the app does not disable the spending action. Confirm the task’s saved Paid Reaction state whenever you intend to stop it.