Slackify — Discuss Velocity
by Broadmax (Drysharks Consulting & Trading Ltd.) https://www.broadmax.com.tr| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Project (project) |
| Lines of code | 852 |
| Technical Name |
slackify |
| License | OPL-1 |
| Website | https://www.broadmax.com.tr |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Project (project) |
| Lines of code | 852 |
| Technical Name |
slackify |
| License | OPL-1 |
| Website | https://www.broadmax.com.tr |
Slackify — Discuss Velocity
Your team never misses what matters — every update on every deal, invoice, and project flows directly into your team channels. Inside Odoo, in real time.
Stop chasing updates. Let them come to you.
How many times has your sales manager asked "What's the status of this order?" and someone had to stop what they were doing, open the record, read through the chatter, and copy-paste the answer into a chat message?
Slackify eliminates that completely. You subscribe a channel to a document once — and from that moment on, every note, every update, every internal message posted on that document automatically appears in the channel, with a direct link back to the record.
Your #sales channel gets notified the moment a sales rep adds a note to a deal. Your #accounting channel gets the update when an invoice is flagged for follow-up. Your #project-alpha channel sees every task comment as it happens. No forwarding, no copy-pasting, no asking around. The right people are always in the loop — automatically.
How it works — in 30 seconds
Open any sale order, invoice, project, or any other document in Odoo. You will see a # button in the chatter toolbar — right next to the followers button you already know. Click it, pick a channel, and you are done. Every message posted in that chatter from now on will also appear in that channel, signed with the document name and a clickable link to open it instantly.
You can connect one document to multiple channels. You can connect multiple documents to the same channel. A single #operations channel can follow your top 10 active deals simultaneously — your team sees the full picture in one place without switching between records.
Real-world examples
Sales team stays aligned
Subscribe your key deals to #sales. When the account manager leaves a note — "customer asked for a revised quote" — the whole team sees it instantly. No status meeting needed.
Finance never chases invoices
Connect overdue invoices to #accounting. Every follow-up note, every payment confirmation, every escalation appears in the channel as it happens. The finance team works from one feed, not ten open tabs.
Operations knows before being asked
Link a delivery order to #logistics. When the sales rep notes a special handling instruction, the warehouse team already sees it — before the shipment is packed.
Project teams stop switching context
Subscribe a project to #project-alpha. Task updates, blockers, and decisions made in the chatter feed directly into the team channel. Everyone stays in sync without leaving their conversation.
More tools included
! Record Mentions
Type ! in any message to search and link a specific record — a sale
order, invoice, task, or product line — directly in your message. The recipient
clicks the link and lands on the record. No more "which order are you talking about?"
/todo — Turn any message into a task
Type /todo Call the customer back in any channel and a project task
is created and assigned to you instantly. A confirmation with a direct link
appears in the channel so nothing falls through the cracks.
/meet — Start a video call instantly
Type /meet to start a video call in the current channel right away.
No scheduling, no external tool, no link to share. Your team is one command away.
Smart contextual search
The ! search knows where you are. Inside a sale order chatter it
shows that customer's other documents. Inside a project channel it shows only
that channel's linked records. Always relevant, never a flood of results.
! Record Mention — Context-Aware Search
Where you type ! |
What you get |
|---|---|
| A named Discuss channel | Only documents subscribed to that channel via the # button |
| A document chatter (e.g. Sale Order) | Related documents — same customer's orders, invoices, tasks |
| Direct / group message | Disabled — no meaningful context there |
Searchable record types
| Record | Searches by |
|---|---|
| Sale Order | Order name, customer name |
| Sale Order Line line | Product, description, order ref, customer |
| Purchase Order | Order name, vendor name |
| Purchase Order Line line | Product, description, order ref, vendor |
| Invoice / Credit Note | Invoice number, reference, customer/vendor name |
| Invoice Line line | Product, description, invoice ref, partner |
| Project Task | Task name, project name |
| Project | Project name |
| CRM Lead / Opportunity | Name, customer name |
| Transfer (stock.picking) | Reference, origin, partner |
| Transfer Line line | Product, picking ref, partner |
| Employee | Name, department, job position |
All line-item searches link to the parent document (e.g. a sale order line
mention opens the sale order form). Line items only appear in the search when there is a typed
search term — they are excluded from the discovery list shown when you first type !.
Permissions & access control
- Channel subscriptions: regular users can only subscribe channels they are a member of. Administrators can subscribe any channel to any document.
-
Record access:
!search respects existing Odoo record rules — users only see records they have read access to. - Forwarded messages: channel members can see forwarded message metadata (document name, link) regardless of whether they have direct access to the source document. Message body is forwarded as-is, so sensitive content in chatter notes will be visible to channel members.
Technical notes
- Depends on
mailandprojectonly. - Sale, purchase, accounting, inventory, and HR models are searched optionally — if the corresponding module is not installed, those record types are silently skipped.
- No external services, no API keys, no webhooks. 100% on-premise.
- All frontend code uses Odoo 18 OWL 3 patterns and the standard patch mechanism — no monkey-patching of private internals.
- Tested on Odoo 18.0 Community and Enterprise.
Changelog
| Version | Changes |
|---|---|
| 18.0.2.0.0 |
Context-aware ! search (channel / chatter / DM routing);
order line search across sale, purchase, invoice, transfers;
channel subscription access control (member-only for regular users);
forwarded message links navigate client-side without page reload.
|
| 18.0.1.0.0 |
Initial release: ! record mentions, # channel subscriptions
on documents with chatter forwarding, /todo and /meet
slash commands.
|
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module