Creating timeline activity via rules?

+1 This would be a very helpful feature, on our case we would like to create timeline entries automatically from slack messages.

Looking forward to this  

Adding my use cases:

1. Deprecating some attributes on the Company object, don’t want to completely remove the fields from the object, don’t want to create a new object to historically track this data so was hoping to add them as a timeline activity on the account so the information is not lost.
2. Creating a fully automated tech touch journey includes adding timeline activities for unassigned accounts where we know when a customer completes certain activitees based on data triggers.

Thanks for sharing the use cases for this request. At this point, it’s not a part of our near term roadmap but will discuss more on this internally. Will update this thread once we have clarity on priority for this item.

I’m sure it’s been mentioned, we also would benefit from this. Our use case is ingesting data from other external sources, and using that to create timeline activities from within rules engine. And being able to do this outside of creating an external action and using an API, or being limited to only creating Milestone activity types

Piling on to this multi-year issue:

It isn’t just about creating timeline entries but also tagging certain parameters.

Use case for us:

Everytime a person mentioned _____ (word) in the body or subject, we want to flag the email.  This seems like a beyond needed feature to be able to update/create timeline entries that are NOT milestones.

Hi Everyone, 
Thank you for your patience on this one. 

As you may know, we've been expanding our MCP and API capabilities, which will continue offer more ways to create and update Timeline activities more programmatically.

That said, I'd love to reassess this request for native Rules Engine support for Timeline. Is this still on your radar? And if so, which workflows and corresponding actions would be needed the most?

Your input will help us prioritize — looking forward to hearing from you!

​@ChiragJ 

This is definitely still on the radar.  MCPs are great for single use items, but we (at my company) have many use cases, and building APIS AND using the limited API calls on creating timelines is time-consuming and eats away from the pool of APIs.

Here are some key items we would love to be able to do:

1. Update specific fields when events happen (i.e., I want to check this box if these requirements are met)
2. Mass create timeline entries for events (like QBRs)
3. Be able to change the author of timeline events (i.e., author has left and someone else needs to be able to edit and we don’t want to allow the user to edit ALL timeline entries)
4. Auto-creation of non-milestones

There are other use cases for us, but hopefully this provides insight of some of the items that would still be great to be able to control via the rules engine!

Definitely still on my radar. Currently working around this for very specific cases with external actions using the Timeline API, but that’s very inflexible. The MCP is useful for creating Timeline entries as well, but for standard, regular, deterministic automations, I’d rather set it up via Rules Engine if possible.

Agreed -- and there are those of us whose LLM rollout (and use of MCP) is more restricted, which makes Rules Engine a much better alternative.

+1 to all of this. We share the exact same use cases and limitations.

Rules Engine provides OOTB log history, execution tracking, and reporting. Handling this via APIs creates an operational "black box" that is much harder for CS Ops to troubleshoot