HomeModulesOther ToolsSocial Publishing | Schedule & Post to Telegram, Discord, Slack
Social Publishing | Schedule & Post to Telegram, Discord, Slack
Other ToolsAuraOdoo Verified

Social Publishing | Schedule & Post to Telegram, Discord, Slack

Write once, schedule, and publish to every channel from Odoo

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
Odoo
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
1034 lines (Python / XML / JS)

Overview & Description

Odoo 19 Odoo 20 Community and Enterprise OPL-1 Version 19.0.1.0.0 Social Publishing Write once, schedule, and publish to every channel from Odoo Community: Telegram, Discord, Slack, Microsoft Teams and any webhook. Your own bot tokens. No subscription, no relay, no per-post fee. Every send is logged with the platform's own message id, and every link is tracked per channel. Module Overview What this module solves. The missing middle Odoo's Social Marketing is an Enterprise app. What Community has is a handful of text fields on the company record so a website footer can render links. There is nothing in between: nowhere to write a post, pick channels, schedule it and have Odoo send it. This is that. Your credentials, your database Channels connect with your own bot token or webhook URL. Nothing sits between your database and the platform: no relay service, no subscription, no per-post fee, and no third party holding your keys or counting your posts. A tracked link per channel, not per post. Four hundred clicks is not a number anybody can act on. Telegram 380 and Discord 32 is, and it costs one link tracker per channel using Community's own link-tracking model. Key Features Everything included in the module. Channels Discord, Slack, Microsoft Teams and any generic JSON webhook Telegram channels and groups, via a bot token One record per destination, not per platform Test Connection sends a real post saying it is a test The last failure is kept on the channel, so a revoked token is visible Channels can be archived; posts already sent through them survive Writing A Post One message, any number of channels A link placeholder anywhere in the text becomes the tracked short link Images attached to the post, sent where the platform accepts an upload A length warning naming the channel that would refuse it, and by how much Post Now, or a date and Schedule Kanban by status, a calendar of what is scheduled, and a list Sending A cron every ten minutes sends what is due Results are built before anything goes out Each channel sends in its own savepoint A failure is recorded, not raised, so one bad webhook cannot kill the run Three retries at 5, 30 and 120 minutes, then it stops asking Retry by hand from the post or from the result row The Record One result row per channel, per post What was actually sent, tracked link and all The platform's own message id, and a permalink where it gives one The error text, the attempt count and when the next attempt is due Sent rows cannot be edited or deleted, by anyone A published post cannot be deleted or cancelled; a draft can Attribution A tracked short link per channel, so clicks split by destination Built on Community's own link tracker, with no new model or redirect Each link carries the campaign and a medium of Social Post The source is named after the channel it went to Click counts roll up to the post and to the channel Tracking can be switched off per post, sending the plain URL Security Two roles: User writes and schedules, Administrator connects channels A User cannot read a bot token or a webhook URL Credentials are field-level restricted, not merely hidden in a view A User cannot create or edit a channel Credentials live on the channel, never in a shared system parameter Multi-company record rules on channels, posts and results Business Benefits Why it matters. No Subscription Your own tokens talk straight to the platform. There is no monthly fee and no cap on how many posts you send. Never Post Twice Each send is isolated, so a later failure can never roll back the row recording a post that is already public. Know What Worked Clicks split by channel, carrying your UTM campaign, so the reporting joins up with the rest of your marketing. Catch Problems Early Length is checked while you are still on the form, and Test Connection proves a channel works before a real post depends on it. Screenshots A tour of the interface. The Composer Screenshot Placeholder One message, the chosen channels, and the live length warning. Delivery Results Screenshot Placeholder One row per channel, with message ids, errors and retry buttons. Channel Setup Screenshot Placeholder Platform, credentials, character limit and Test Connection. Scheduled Calendar Screenshot Placeholder What is going out and when, across the month. Workflow From a blank post to click counts. Connect a channel. Paste a Discord, Slack or Teams webhook URL, or a Telegram bot token and your channel name. One record per destination. Test the connection. It sends a real post that says it is a test, because every one of these platforms will accept a token and then refuse the post. Write the post. One message, the channels you want, an image if the platform takes one, and a link placeholder wherever the tracked link should go. Check the warning. If the message outgrows a channel's limit the form says which channel and by how many characters, while you can still fix it. Post now or schedule. A result row is prepared for each channel first: exact text rendered, link minted, length checked. Then the cron sends what is due. Read the results. Each row shows sent or failed, the platform's message id, a permalink where there is one, and the error and next attempt where there is not. Post Status Status Meaning Can be deleted Draft Being written, nothing prepared yet Yes Scheduled Result rows built, waiting for its time Yes Posting The run is under way No Posted The run finished and at least one channel took it No Failed The run finished and no channel took it No Cancelled Called off before publishing Yes Configuration Menus, platforms, limits and roles. Menu Structure Menu Purpose Social, then Posts Write, schedule and publish, in kanban, calendar and list Social, then Delivery Results Every send, with its message id, error and retry state Configuration, then Channels Destinations and their credentials, administrators only User Roles Action User Administrator Write, schedule and publish posts Yes Yes Read delivery results Yes Yes Create or edit a channel No Yes Read a bot token or webhook URL No Yes Credentials are restricted at field level, so a User cannot reach them through a different view, an export or the API either. Platforms And Their Limits Destination Connect with Character limit Images Telegram A bot token and the channel name 4096 Yes Discord A channel webhook URL 2000 By link Slack An incoming webhook URL 3000 By link Microsoft Teams An incoming webhook URL 28000 By link Generic JSON webhook Any URL that accepts a JSON body No limit applied By link The three webhook formats are not interchangeable. Discord, Slack and Teams each disagree about what the text field is called and reject the others' shape, so the channel carries a Webhook Format setting and the correct body is sent for each. Technical Details Models, dependencies and design. Module Information Technical Name social_publish_aura Version 19.0.1.0.0 Category Marketing / Social Marketing License OPL-1 Dependencies mail, utm, link_tracker External Libraries None beyond a standard Odoo installation Third-Party Relay None. Your database talks to the platform directly. Scheduled Job Send scheduled posts, every 10 minutes Automated Tests 52 tests, including a browser tour. No test reaches the network. Models Model Description social.channel A destination, its credentials and its capabilities social.post The message, its channels and its schedule social.post.target One send: what went out, where, and what came back Attribution reuses Odoo's own link tracker and UTM models rather than adding a tracking model or a redirect route of its own. Design Notes Each send has its own savepoint. A connector that raises after the platform accepted the post must not roll back the row saying so, or the next run would post it again. Duplicate posting is the one failure a publisher cannot have. Results are prepared up front. Text rendered, link minted, length checked while somebody is still looking at the form, rather than at nine the next morning. One HTTP seam. Every connector goes through a single method, so a proxy, a timeout or a rate limiter is configured once, and a test run can never post to a real server. A new platform is one value and one method. The connector contract is documented and typed; the character limit and image support are overridable hooks. Failures are recorded, not raised. A cron sending twenty posts does not die on the first bad webhook. Timeouts, dead hosts and HTTP 500s are all stored with their reason, and a Telegram reply that returns 200 while reporting failure is treated as the failure it is. Compatibility Where the module runs, and what it reaches. Item Supported Odoo Version 19.0 Current Hosting Odoo.sh, On-Premise and any self-managed deployment Outbound Access Required. The server must be able to reach the platform's API. Multi-Company Yes, with record rules on channels, posts and results Multi-Language Yes, all labels and messages are translatable Mobile and Tablet Yes, standard responsive Odoo web client UTM and Link Tracking Yes, using Odoo's own campaign and link-tracker models What Ships Here, And What Needs Paperwork Platform In this module Access needed Discord, Slack, Teams, any webhook Included A URL from the channel settings Telegram Included A bot token from BotFather Facebook Page, Instagram Business Separate module Your own Meta app, plus App Review LinkedIn organisation pages Separate module Community Management API approval X / Twitter Separate module A paid API tier The two connectors shipped here were chosen because they need no application review and no paid tier, so you can install this and post within minutes. Platform terms change often; check the bottom three before committing. Supported Editions Both editions, one code base. Community Edition Supported The edition this module exists for. It brings scheduled publishing to an Odoo whose social features are eight text fields. Enterprise Edition Supported Runs on Enterprise with its own models, useful for the chat platforms Social Marketing does not cover. Odoo.sh Supported No extra Python packages to install. Make sure outbound HTTPS to the platforms you use is permitted. Installation Four steps to your first post. Copy the module. Place the social_publish_aura folder in your Odoo addons path, then update the apps list from developer mode. Install Social Publishing. Mail, UTM and Link Tracker are installed with it as dependencies. Add a channel. Social, then Configuration, then Channels. Paste a webhook URL, or a Telegram bot token and channel name, then press Test Connection. Assign the roles and post. Give marketers User and whoever holds the credentials Administrator, then write your first post. The sending job is created on install and runs every ten minutes, but it only ever sends posts you have scheduled. Nothing goes out until you write something and schedule it. Frequently Asked Questions The questions asked most often. No. Channels use your own bot token or webhook URL and your database talks to the platform directly. There is no relay service in the middle, so nothing meters your posts and nobody else holds your credentials. Telegram, Discord, Slack, Microsoft Teams and any endpoint that accepts a JSON webhook. These were chosen because they need no application review and no paid tier. Facebook, Instagram, LinkedIn and X are separate modules, because each needs approval or payment before it can post at all. Each send runs in its own savepoint, so the successful one stays recorded as sent and the failed one is marked failed with its reason. This matters more than it sounds: rolling back the record of a post that is already public would make the next run send it a second time, and no rollback retrieves a message from the internet. Three times, at five minutes, thirty minutes and two hours, then it stops asking rather than hammering a dead endpoint forever. You can also retry by hand from the post or from the individual result row, once you have fixed whatever was wrong. Each channel gets its own tracked short link, so the numbers arrive split by destination rather than as one meaningless total. Every link carries your UTM campaign and a source named after the channel, and the counts roll up to both the post and the channel. Tracking can be switched off per post if you would rather send the plain URL. No. Tokens and webhook URLs are restricted at field level to administrators, so a User who writes and schedules posts cannot read them through a different view, an export or the API. Credentials live on the channel rather than in a system parameter shared across the whole database. No, and deliberately. A published post cannot be deleted or cancelled, and a sent result row cannot be edited or deleted by anybody. Cancelling it in Odoo would only hide it from you while it stayed live on the platform, and a record anybody can tidy up is not a record. Drafts can be deleted freely. No. This publishes; it does not listen. There is no inbox, no follower count and no engagement graph, because those need a different half of each API and permissions this module deliberately does not ask for. It also posts what you write: automatic posting when a record changes belongs in an automation module built on top of this one. Changelog Release history. Version 19.0.1.0.0 Initial Release Telegram channels and groups via your own bot token Discord, Slack, Teams and generic JSON webhook channels Correct payload shape per webhook format, with per-platform limits Test Connection that sends a real post before you rely on a channel One post to many channels, with images where supported Live length warning naming the channel and the overrun Post now or schedule, with a calendar of what is due Sending job every ten minutes, with results prepared up front Per-channel savepoints so one failure cannot undo a public post Three automatic retries at 5, 30 and 120 minutes, plus manual retry Platform message id and permalink recorded per send Immutable sent rows; published posts cannot be deleted or cancelled A tracked link per channel carrying your UTM campaign User and Administrator roles with field-level credential protection 52 tests and a browser tour, none of them touching the network Support We answer, and we keep our modules current. Email odooaura@gmail.com Website www.auraodoo.tech YouTube youtube.com/@Auraodoo Free support for bug fixes on the Odoo version you downloaded. Customisation and installation help available on request. Aura Odoo Tech Odoo modules built to be understood, not just installed. Odoo 19 OPL-1 social_publish_aura www.auraodoo.tech | odooaura@gmail.com | youtube.com/@Auraodoo

Key Capabilities & Features

  • Discord, Slack, Microsoft Teams and any generic JSON webhook
  • Telegram channels and groups, via a bot token
  • One record per destination, not per platform
  • Test Connection sends a real post saying it is a test
  • The last failure is kept on the channel, so a revoked token is visible
  • Channels can be archived; posts already sent through them survive
  • One message, any number of channels
  • A link placeholder anywhere in the text becomes the tracked short link
  • Images attached to the post, sent where the platform accepts an upload
  • A length warning naming the channel that would refuse it, and by how much
  • Post Now, or a date and Schedule
  • Kanban by status, a calendar of what is scheduled, and a list
  • A cron every ten minutes sends what is due
  • Results are built before anything goes out
  • Each channel sends in its own savepoint
  • A failure is recorded, not raised, so one bad webhook cannot kill the run
  • Three retries at 5, 30 and 120 minutes, then it stops asking
  • Retry by hand from the post or from the result row
  • One result row per channel, per post
  • What was actually sent, tracked link and all
  • The platform's own message id, and a permalink where it gives one
  • The error text, the attempt count and when the next attempt is due
  • Sent rows cannot be edited or deleted, by anyone
  • A published post cannot be deleted or cancelled; a draft can
  • A tracked short link per channel, so clicks split by destination
  • Built on Community's own link tracker, with no new model or redirect
  • Each link carries the campaign and a medium of Social Post
  • The source is named after the channel it went to
  • Click counts roll up to the post and to the channel
  • Tracking can be switched off per post, sending the plain URL
  • Two roles: User writes and schedules, Administrator connects channels
  • A User cannot read a bot token or a webhook URL
  • Credentials are field-level restricted, not merely hidden in a view
  • A User cannot create or edit a channel
  • Credentials live on the channel, never in a shared system parameter
  • Multi-company record rules on channels, posts and results
  • Connect a channel. Paste a Discord, Slack or Teams webhook URL, or a Telegram bot token and your channel name. One record per destination.
  • Test the connection. It sends a real post that says it is a test, because every one of these platforms will accept a token and then refuse the post.
  • Write the post. One message, the channels you want, an image if the platform takes one, and a link placeholder wherever the tracked link should go.
  • Check the warning. If the message outgrows a channel's limit the form says which channel and by how many characters, while you can still fix it.
  • Post now or schedule. A result row is prepared for each channel first: exact text rendered, link minted, length checked. Then the cron sends what is due.
  • Read the results. Each row shows sent or failed, the platform's message id, a permalink where there is one, and the error and next attempt where there is not.
  • Each send has its own savepoint. A connector that raises after the platform accepted the post must not roll back the row saying so, or the next run would post it again. Duplicate posting is the one failure a publisher cannot have.
  • Results are prepared up front. Text rendered, link minted, length checked while somebody is still looking at the form, rather than at nine the next morning.
  • One HTTP seam. Every connector goes through a single method, so a proxy, a timeout or a rate limiter is configured once, and a test run can never post to a real server.
  • A new platform is one value and one method. The connector contract is documented and typed; the character limit and image support are overridable hooks.
  • Copy the module. Place the social_publish_aura folder in your Odoo addons path, then update the apps list from developer mode.
  • Install Social Publishing. Mail, UTM and Link Tracker are installed with it as dependencies.
  • Add a channel. Social, then Configuration, then Channels. Paste a webhook URL, or a Telegram bot token and channel name, then press Test Connection.
  • Assign the roles and post. Give marketers User and whoever holds the credentials Administrator, then write your first post.
  • Telegram channels and groups via your own bot token
  • Discord, Slack, Teams and generic JSON webhook channels
  • Correct payload shape per webhook format, with per-platform limits
  • Test Connection that sends a real post before you rely on a channel
  • One post to many channels, with images where supported
  • Live length warning naming the channel and the overrun
  • Post now or schedule, with a calendar of what is due
  • Sending job every ten minutes, with results prepared up front
  • Per-channel savepoints so one failure cannot undo a public post
  • Three automatic retries at 5, 30 and 120 minutes, plus manual retry
  • Platform message id and permalink recorded per send
  • Immutable sent rows; published posts cannot be deleted or cancelled
  • A tracked link per channel carrying your UTM campaign
  • User and Administrator roles with field-level credential protection
  • 52 tests and a browser tour, none of them touching the network
  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

1 image available
Social Publishing | Schedule & Post to Telegram, Discord, Slack screenshot 1
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.