Confirm the Telegram destination for Cloudinary media
Check the current chat details before sharing an asset so a stale chat name or username is easier to catch.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Why this helps
A renamed or mistyped Telegram destination can send a time-sensitive asset to the wrong place or nowhere at all.
- Retrieve up-to-date information for the Telegram chat involved in a sharing request.
- Give the workflow a chance to surface destination details before sending media.
- Reduce mistakes caused by outdated chat names or usernames.
Setup
Build it in a few focused steps.
- 1Connect Cloudinary and Telegram once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for destination checks.
- 3Tell Notis to look up the Telegram chat named in each request and report its current details before the Cloudinary asset is shared.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with a real Telegram chat and verify the returned chat details.
Questions about this workflow
Does this action send the Cloudinary media too?
No. This Telegram action gets chat information. Sending media would require a separate automation using a Telegram send action.
What does the workflow need to check a chat?
The webhook request needs to identify the Telegram chat. The action returns current chat information such as its name or username.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudinary to Telegram. A trigger fires from one place; an action lands in another.
Cloudinary triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Cloudinary and Telegram, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Telegram.