Social finally lands ON the record - and flows can act on the person who commented

Social was in the CRM without being on the record, and this closes that. Comments and direct messages now appear on the contact's timeline, next to their emails, calls and meetings. Before this, someone who commented on your Instagram post could become a contact - and then you'd open that contact and find nothing there, with no sign of the interaction that created them. Each entry shows what was said, on which platform, and links back to the post. The timeline entry is a mirror: the conversation itself stays in the inbox, and the moderation log keeps its own record. A published post deliberately does not appear on individual contacts - a brand post isn't about any one person, and a timeline full of everything your company ever posted would bury the things that actually involve them. Flows can now act on the person, not just hear about them. The social comment and DM triggers now enrol the matched contact, so a flow can update a field, add them to a list, send them an email or route them to an owner - the ordinary things you'd expect. Until now those triggers passed information a flow could read but no record it could work on, which made them useful for notifications and little else. And flows can publish. A new Publish social post step schedules a post to your connected accounts, so "new case study added → post about it" is a flow rather than a reminder to yourself. It creates the scheduled post and stops there - the normal publishing engine sends it, which means a post created by a flow gets exactly the same platform checks, daily-limit handling, retries and audit trail as one you wrote by hand.