Salesforce · Chatter · Activity Automation

Chatter to Task Automation in Salesforce: Turn Posts and Comments into Tracked Tasks

Next steps get agreed in Chatter every day, and most of them never become a Salesforce Task. This guide compares the ways to close that gap: native post actions, Flow, Apex, and Twopir's free AppExchange app. It covers how the #task syntax works, how to roll it out safely, and what the Summer '26 Chatter change means for your org.

Key Takeaways

  • A Chatter post is not a Task. It never appears in My Tasks, Task list views or Activities reports, so commitments made in Chatter are invisible to the people who track follow-up.
  • Salesforce's native Create New Task post action needs a click per task and assigns the task to whoever creates it, not to the person who was asked to do the work.
  • Chatter to Task automation reads the post itself: #task starts a block, @User sets the owner, each numbered line becomes a Task, and #date sets the due date.
  • Twopir's Chatter Activity to Task Automation is a free, native managed package on AppExchange, currently in beta. It works on posts and comments and can set default due dates.
  • Since Summer '26, Chatter is off by default in new orgs, though existing orgs keep it. Check Chatter Settings before planning any feed-based automation.

What is Chatter to Task automation? It is automation that turns a structured Chatter post or comment into one or more Salesforce Task records. You don't fill in a separate form. The post names the owner, the action and the due date, and the automation creates the Task with that owner, subject and due date, linked to the record the conversation happened on. The agreement and the follow-up become the same step.

We first published this guide in April 2026, when we launched the app. This version is rebuilt from Salesforce's current documentation, checked in October 2026. It adds a comparison of every way to create Tasks from Chatter, the Summer '26 change to Chatter defaults, a rollout plan, the pitfalls we see, and a way to measure the result without guessing. It is written for Salesforce admins, sales and service operations, and RevOps leaders at growing and mid-market companies whose teams already agree next steps in Chatter.

Section 01 · Short Answer

What Does Chatter to Task Automation Actually Do?

It watches new Chatter posts and comments for a trigger tag, reads who should do what and by when, and creates one Salesforce Task per action item. Each Task gets the mentioned user as owner, the action as subject and a due date, and is linked to the record the post was made on. People keep talking in Chatter. Salesforce gets real, reportable Tasks.

Actionable Tasks Automatically: a Chatter post with two #task blocks, one for @TCPL Support and one for @TCPL Consultant, each with numbered action items and an optional #date; a parsing engine detects #task, the assignee, numbered subjects and the date, and applies today plus the TaskActivityDate value when no date is given; assignment logic assigns each task to the mentioned user and links it to the related record; the result is Salesforce Tasks with assignee, subject, related record and due date
How Chatter Activity to Task Automation turns one post into several Tasks: parse, assign, date, create.

Captured where it is said

The Task is created from the post or comment itself, so nobody has to remember to open the Activity tab later.

Owned by the right person

The @mentioned user owns the Task, so it lands in their My Tasks list, not in the list of the person who typed the post.

Visible in reports

Tasks appear on the activity timeline, in Task list views and in Activities reports. Chatter posts do not.

Section 02 · The Gap

Why Do Follow-Ups Agreed in Chatter Get Lost?

Because Salesforce treats a Chatter post and a Task as different things. A post is a conversation entry on a feed. A Task is an activity record with an owner, a status and a due date. Every place people check for work to do, such as My Tasks, Task list views, the activity timeline and Activities reports, reads Tasks. None of them reads posts.

What you needChatter post (FeedItem)Salesforce Task
A named ownerAn @mention notifies someone, but nobody owns the actionOne owner (a user or a queue) per Task
A due dateOnly as free textDue Date field (ActivityDate), used by list views and reports
A statusNoneNot Started, In Progress, Completed and other values
Shows in My Tasks and on HomeNoYes
Activities reportsNoYes, by owner, status, due date and related record
If it is deletedHard deleted, with no Recycle BinStandard record behaviour

The field details come from Salesforce's Task object reference and FeedItem object reference. Salesforce's task tracking guide lists where Tasks surface: Task list views for today, open, overdue and recently completed work, the Home page, the activity timeline and Activities reports.

The result is familiar. A deal review in an Opportunity feed ends with "Can you send the revised quote by Friday?" Everyone reads it, the rep says yes, and nothing in Salesforce records that the quote is owed. The pipeline report shows no open activity, and the manager finds out on Monday. This is not a discipline problem. Asking people to re-enter in a form what they have just written in a post is a process design problem.

Section 03 · Options

What Are the Ways to Create a Salesforce Task from a Chatter Post?

There are five: create the Task by hand, use the native Create New Task post action, build a record-triggered Flow, write an Apex trigger, or install an app that parses the post. The first two depend on someone remembering to click. The last three run automatically. They differ in who owns the Task, whether comments count, and who maintains the logic.

OptionTask ownerSeveral tasks from one postComments tooEffort
1. New Task on the Activity tabWhoever the creator picksNo, one form eachn/aNone to build
2. Create New Task post actionThe person who clicks itNo, one click eachUser-written posts onlyAdmin setting
3. Record-triggered Flow on FeedItemWhatever your logic setsPossible, but hard to parseConfirm for FeedCommentBuild and maintain
4. Custom Apex triggerWhatever your code setsYesYes, with a FeedComment triggerCode, tests, upkeep
5. Chatter Activity to Task AutomationThe @mentioned userYes, numbered lines and several #task blocksYes, switchableInstall and configure

1 and 2: the native options

In Lightning Experience, the New Task action sits on the record's Activity tab, while the Chatter tab holds Post, Poll and Question, as Salesforce's actions in Lightning Experience page describes. Admins can also add Create New Task to the post menu through Feed Item Layouts, provided actions in the publisher and feed tracking for Tasks are enabled. Salesforce's post action setup guide notes that the action only works on user-written posts and that its fields are fixed. The user guide adds that a task created this way "is assigned to you." That suits personal reminders, but it doesn't help with delegation, which is what most Chatter follow-ups are.

3: Flow

Record-triggered flows can run on FeedItem: Salesforce's FeedItem reference mentions them directly. Creating a Task needs an after-save flow, because before-save flows can only update the triggering record. The hard part is parsing: finding the trigger tag, matching a mentioned name to a user, splitting numbered lines and reading a date, all with Flow formulas. In our experience this works for one fixed pattern and becomes brittle as soon as people write freely. We found no official confirmation that record-triggered flows support FeedComment, so test that in a sandbox before relying on comments.

4: Apex

Salesforce's Apex guide states that you can write triggers for the FeedItem and FeedComment objects. Insert triggers fire only for user-created types such as text, link, question and content posts. A custom trigger gives full control, but you then own the parser, its test coverage, bulk handling, error handling and every future change. This is the right path if you need logic that no packaged app offers, such as routing to queues or setting custom Task fields.

5: a packaged app

An app gives you the Apex approach without writing or maintaining the code. The rest of this guide uses Twopir's Chatter Activity to Task Automation as the example, because we built it for this problem.

Section 04 · How It Works

How Does the #task Syntax Turn a Chatter Post into Tasks?

Four tags do the work: #task starts a block, @User names the owner, each numbered line becomes one Task subject, and #date MM/DD/YYYY sets that line's due date. A post can hold several blocks, one per owner, so a single update can delegate work to several people. Lines without a date get a default due date.

You typeWhat it doesTask field
#taskStarts a task block in the post or comment(trigger)
@User NameNames the person who will do the workAssigned To (OwnerId)
1. 2. 3. …Each numbered line becomes its own TaskSubject
#date 11/06/2026Sets the due date for that line (month/day/year)Due Date (ActivityDate)
(no #date)Today plus the TaskActivityDate offset, or today if no offset is setDue Date

Here is a comment on an Account record after a renewal call. It creates three Tasks, all related to that Account:

#task @Alex Morgan
1. Send the revised renewal quote #date 11/06/2026
2. Book the security review with their IT lead
 
#task @Sam Lee
1. Check open support cases before the renewal call #date 11/04/2026

Alex Morgan gets two Tasks: the quote, due November 6, and the security review. The review has no date, so it is due today plus the TaskActivityDate offset. Sam Lee gets one Task, due November 4. Each Task is linked to the Account, so it appears on the Account's activity timeline and in reports filtered by that Account.

What admins can configure

  • Default due date. The TaskActivityDate setting holds a number of days. With a value of 5, an undated line is due five days after the post. With no value, it is due the same day.
  • Posts, comments or both. Trigger Settings switch Task creation on or off separately for Chatter posts and for comments.

According to its AppExchange listing, the app is free and installs as a managed package. It runs natively in Salesforce with no external servers or data transfers, supports Lightning, Person Accounts and the Salesforce mobile app, and is in beta (version 0.5.0 at the time of writing). Treat beta status as a reason to pilot in a sandbox first, which you should do with any automation that creates records.

Section 05 · Chatter in 2026

Is Chatter Still Worth Automating After the Summer '26 Change?

Yes, if your org already uses Chatter. From Summer '26, Salesforce switches Chatter off by default in newly created orgs and switches on Salesforce channels, which bring Slack into record pages. Orgs created earlier are not affected, and Salesforce says you can keep using Chatter in existing orgs. It has published no retirement date for Chatter.

The details are in the Summer '26 release note. With Chatter off, the Chatter tab and feed, the Follow button, groups and the Chatter APIs are unavailable. An admin can turn Chatter on under Setup › Chatter Settings, for example to use Case Feed, to collaborate in an Experience Cloud site, or where Slack is not an option. Salesforce also supports a mixed model: Slack internally, Chatter with external users.

Good fit. Orgs created before Summer '26 where teams already discuss deals, cases or matters in record feeds. Service teams that work in Case Feed. Firms that collaborate with clients or partners through Chatter in an Experience Cloud site. Teams without Slack.

Think first. A new org where Chatter is off and the team has moved record collaboration to Salesforce channels in Slack. There, solve the follow-up problem in Slack, for example by adding Slack messages to Salesforce records with the Salesforce app for Slack, rather than turning Chatter back on for one feature.

If you are weighing the two, our guide to Salesforce and Slack integration covers how Slack connects to Salesforce records.

Section 06 · Rollout

How Do You Roll Out Chatter to Task Automation Safely?

Confirm Chatter and feed tracking are on, install in a sandbox, set the default due date and triggers, pilot with one team, then train everyone on a one-line syntax card. Installing takes minutes. Adoption is the real work: people need to know the tags, and managers need to look at the Tasks the posts create.

1. Check Chatter and feed tracking.
→ In Setup › Chatter Settings, confirm Chatter is enabled. Orgs created from Summer '26 have it off by default. Then confirm feed tracking is enabled for each object where people will post, such as Account, Opportunity, Case or your custom objects. Without feed tracking, those records have no feed to post in.
2. Install in a sandbox.
→ Install the managed package from the AppExchange listing into a sandbox. Test posts and comments on each object you care about, including records owned by other teams, so sharing and access behave as you expect.
3. Set the defaults.
→ Choose a TaskActivityDate offset that matches your follow-up standard, for example two business days for sales or one day for support. Decide whether comments should create Tasks as well as posts. For most teams they should, because commitments often appear in replies.
4. Check for collisions.
→ Review existing Task automation, such as flows, validation rules and required custom fields on Task. A validation rule that demands a field the post can't supply will block creation. Open Flow Trigger Explorer to see what else runs when Tasks are created.
5. Pilot with one team.
→ Run it for two to four weeks with one sales pod or support queue. Collect the posts that did not produce the Task people expected, and fix the habit or the setting behind each one.
6. Train with a syntax card.
→ Pin one example post in each team's group: #task @Name, numbered lines, #date MM/DD/YYYY. Explain the date format explicitly to teams outside the US (see Section 08).
7. Deploy and make Tasks the source of truth.
→ Install in production, then change the meeting habit: pipeline and case reviews open the Task report, not the feed. That is what makes people keep using the syntax.

If your Task data is already unreliable, with duplicate automation, old validation rules or inconsistent statuses, clean that up first. A Salesforce health check is a quick way to find what will get in the way.

Section 07 · Use Cases

Which Teams Get the Most from Chatter to Task Automation?

Any team that already agrees work in record feeds: sales on Accounts and Opportunities, support on Cases, RevOps and admins on operational records, and professional services firms on matters. The common thread is delegation. When one person asks others to do things in a feed, automation turns each request into a Task with an owner and a date.

Sales

Deal reviews in Opportunity feeds end with next steps for the rep, the solution engineer and legal. Each becomes a Task on the Opportunity, so stalled deals show missing or overdue activity in pipeline reports.

Customer support

Case Feed escalations name an engineer and an account manager in one comment. Both Tasks sit on the Case, so the Case shows open follow-ups instead of a long thread to re-read.

RevOps and admins

Data-quality fixes, territory changes and renewal preparation agreed in feeds become Tasks on the Account or Opportunity, giving operations work the same audit trail as sales work.

Law firms and consultancies

Matter and engagement records collect instructions from partners to associates and paralegals. Turning each instruction into a dated Task makes deadlines visible to whoever manages the matter.

For sales teams, the Tasks feed straight into the pipeline disciplines in our Sales Cloud services. For law firms running matters in Salesforce, see our legal Salesforce consulting.

Section 08 · Pitfalls

What Should You Watch Out for with Chatter-Based Tasks?

Most problems come from dates, missing feeds and expectations about which posts count, not from the automation itself. These are the issues to plan for before rollout, with the platform rule behind each one.

Date format outside the US. #date reads month/day/year. A UK, Australian or UAE user who types 05/11/2026 meaning 5 November gets a Task due on May 11. Put the format on the syntax card and show one example.
No feed, no Task. Most objects only have a feed when feed tracking is enabled for them, and new orgs from Summer '26 start with Chatter off. Check both before you promise the feature to a team.
System posts don't count. FeedItem triggers fire for posts people write, such as text, link and file posts. They don't fire for system feed events like tracked field changes or created-record events (Salesforce knowledge article 000387951). Tags in an automated post will not create Tasks.
Long subjects. The Task Subject field holds 255 characters. Keep each numbered line to one clear action and put the context in the conversation.
One owner per Task. A Salesforce Task has one owner at a time. To give the same work to two people, write two #task blocks rather than two mentions in one block.
The post can disappear; the Task should not. Feed items and comments are hard deleted, with no Recycle Bin. Treat the Task, not the post, as the record of the commitment, and report on Tasks.
Competing automation. Validation rules or required fields on Task, and other flows that fire on Task creation, can block or change the Tasks the app creates. Test them together in a sandbox.
Section 09 · Measurement

How Do You Measure Whether It Is Working?

Take a baseline from an Activities report before go-live, then compare the same report at 30 and 90 days. Watch four numbers: open Tasks on active Opportunities and Cases, overdue Tasks, Tasks completed on time, and the share of active records with no open Task. Base the result on your own data, not on a vendor's percentage.

MeasureWhere to get itWhat good looks like
Active records with no open TaskOpportunities or Cases with Activities report, filtered to open recordsFalls after rollout
Tasks created per week, by ownerTasks and Events report, grouped by Assigned ToRises, spread across the team rather than one person
Overdue TasksTask list view or report, filtered on Due Date and StatusStays flat or falls as volume rises
Completed on timeCompleted Tasks, completion date against Due DateRises as default due dates are tuned

Salesforce explains how to build these in its activity reports guide. Managers can report on the Tasks of people below them in the role hierarchy, so the same report works for team reviews. If you want follow-ups visible on the record in a custom layout, our guide to building a custom activity timeline in Salesforce Lightning shows one approach. To connect activity to forecast and pipeline health, see our revenue operations services.

Section 10 · Bottom Line

The Bottom Line

Chatter is where many Salesforce teams agree what happens next. Tasks are where Salesforce tracks it. Chatter to Task automation joins the two without adding a step. Twopir Consulting built Chatter Activity to Task Automation for exactly this. We implement, rescue, optimize, and integrate complex CRM and revenue systems, and we can help you roll it out alongside the reports and habits that make it stick.

  1. 1

    Confirm Chatter and feed tracking are on for the objects your teams post on.

  2. 2

    Choose the approach: native action for personal reminders, an app or Apex for delegation.

  3. 3

    Install in a sandbox, set the default due date, and test alongside your existing Task automation.

  4. 4

    Train with one example post, and spell out the MM/DD/YYYY date format.

  5. 5

    Baseline an Activities report, and run reviews from Tasks, not from the feed.

Ready to Start

Turn Chatter Conversations into Follow-Ups You Can Report On

Tell us where your teams agree next steps today and what your managers need to see. We will set up the automation, the defaults and the activity reports that fit your org.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Yes. Admins can add the native Create New Task action to the post menu, but each task needs a click and is assigned to the person who creates it. To create tasks automatically and assign them to the mentioned user, use an Apex trigger, a record-triggered flow on FeedItem, or an AppExchange app such as Chatter Activity to Task Automation.

Both can. Salesforce supports Apex triggers on FeedComment as well as FeedItem. Chatter Activity to Task Automation reads posts and comments, and its Trigger Settings let an admin switch each one on or off. Including comments matters, because many commitments are made in replies to a post rather than in the post itself.

Yes. Salesforce's FeedItem documentation refers to record-triggered flows on FeedItem. Creating a Task needs an after-save flow, because before-save flows can only update the triggering record. Parsing owners, numbered lines and dates out of free text with Flow formulas is fragile, and support for comments should be tested in a sandbox first.

Salesforce has not announced a retirement date. From Summer '26, Chatter is off by default in newly created orgs, where Salesforce channels in Slack are on instead. Orgs created earlier are unaffected and can keep using Chatter, and admins of new orgs can turn it on under Setup, Chatter Settings.

Yes. The AppExchange listing shows it as free and never requiring payment. It installs as a managed package, runs natively in Salesforce with no external servers, and supports Lightning and the Salesforce mobile app. It is currently in beta, so install it in a sandbox and pilot it with one team before rolling it out.

The task still gets a due date. If the admin has set the TaskActivityDate offset, the due date is today plus that number of days, so a value of 5 means five days after the post. If no offset is set, the task is due the same day. Dates you do type use the MM/DD/YYYY format.

Yes. They are standard Salesforce Task records, so they appear in the owner's My Tasks and Task list views, on the related record's activity timeline, and in Activities reports. That is the main reason to convert posts into tasks: a Chatter post on its own appears in none of those places.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, and we publish our own Salesforce apps on AppExchange, including Chatter Activity to Task Automation.