LinkedIn publishing

Native LinkedIn publishing is cron-based and runs after human approval.

LinkedIn is a native publishing platform in CRISP Content Engine: approved content is queued as a publish job and sent to LinkedIn by a scheduled worker.

Who this page is for

Users approving/scheduling LinkedIn posts
Operators setting up cron and troubleshooting status drift

How it works (at a glance)

Users connect LinkedIn in Connections.
Approving content creates/updates publish state for LinkedIn.
A cron worker runs periodically and publishes due items.

Constraints and edge cases

Cron must run (Vercel does not run background cron).
Token expiry happens: re-authentication may be required if publishing fails with auth errors.
Rate limits and API availability are outside CRISP’s control.

Troubleshooting checklist

Confirm cron is calling the LinkedIn due endpoint on schedule.
Confirm the LinkedIn connection is still valid for the user/workspace.
If items are stuck, check the app’s publishing status UI and retry workflows.

Publishing overview: Publishing overview
Content system status model: Content system
Integrations overview: Integrations

Publishing overview

How CRISP Content Engine schedules and publishes content — and where each platform currently sits.

Meta publishing (Facebook + Instagram)

Native publishing to Facebook Pages and Instagram Business accounts — available on Growth tier and above.