Connect Telegram to Forcemanager
When something happens in Telegram, Notis takes the next step in Forcemanager. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Telegram to Forcemanager
Turn deal updates into ForceManager activity notes
Send a Telegram deal update and have Notis add its useful context to the matching ForceManager activity.
Correct company details from Telegram
Turn a clear correction shared in Telegram into an update to the matching ForceManager company record.
Save channel sales briefs to activities
Use a Telegram channel post as the source for updating a related ForceManager activity with a concise sales brief.
Log a customer touch with one tap
Let a Telegram inline button confirm that a customer touch should be recorded on its existing ForceManager activity.
Refresh activity context after a message edit
When a Telegram message is edited with corrected deal information, update the referenced ForceManager activity with the latest context.
Refresh company context when a sales group member joins
When a new member joins a Telegram sales group, update the relevant ForceManager company context with the onboarding detail provided for that member.
Look up a company from a Telegram request
Ask for a company in Telegram and have Notis retrieve its ForceManager record for a quicker response.
Check an activity from Telegram
Request an existing ForceManager activity in Telegram and have Notis retrieve its current details.
Resolve CRM references from channel updates
Use an external reference shared in a Telegram channel post to look up its ForceManager internal ID mapping.
Supported Triggers and Actions
Notis builds workflows that link Telegram to Forcemanager. A trigger fires from one place; an action lands in another.
Telegram triggers
Forcemanager actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Activity
Delete an existing activity by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Company
Tool to delete a company by its ForceManager ID. Use when you need to remove an existing company from the system.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Delete Contact
Delete an existing contact by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Delete Sales Order
Delete a sales order by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is non-JSON, capturing response text.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Delete Sales Order Line
Delete a sales order line by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is HTML instead of JSON, capturing the response text as a message.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Delete Master Data Value
Delete a master-data value (Z_ table) by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is HTML instead of JSON, capturing the response text as a message. Also retries sending authentication headers as query parameters on HTTP 401 as some gateways expect them in query string.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Delete View
Delete a saved view by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
Get Activity
Tool to get a single activity by ID. Use when you need to fetch a specific activity. Returns empty entity with found=False on non-JSON HTML or if not found.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Telegram and Forcemanager
Connect any two apps with Notis in the middle.
Telegram and Forcemanager, 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 Forcemanager.