Publishing flow
Personal
Cowork → POST /api-v2-posts (target=personal, scheduled_at=...)
→ ProPresence stores post
→ at scheduled_at, ProPresence calls LinkedIn API with user's token
→ LinkedIn URN stored back on the post
Brand
Cowork → POST /api-v2-posts (target=brand, no scheduled_at)
→ ProPresence stores draft
User reviews in /posts (Brand context) → sets scheduled_at
→ ProPresence emits post.scheduled event
→ Make.com webhook fires
→ Make scenario calls LinkedIn Company Page Share API
→ Make scenario POSTs back to /make-post-callback
→ ProPresence marks post Published, stores live_url
The make-post-callback step is what flips the post from Scheduled → Published in ProPresence. Without it the post still goes live on LinkedIn but ProPresence can’t tell.
Related: Scheduling rules, Make.com webhook setup, Post callback