Social Marketing

Your team has useful material to share, but turning it into a consistent publishing week means finding the source, checking the copy, choosing the right company page and remembering the schedule. Social Marketing keeps that work together, so you can review a batch once and follow each post through to its publication receipt.

Connect your company page

Enable Social Marketing in Plugins, then open Social Marketing → Setup. Your operator supplies the Postiz publishing service, while each workspace connects its own Postiz organization and LinkedIn company page. Enter that organization's API key in the secure connection field, then choose Verify and connect to check its identity.

The plugin settings hold your brand guidance, weekly scheduling time zone and optional weekly draft preparation. Keep API keys in the connection field, because ordinary settings are visible to people using the workspace. Your operator can follow the Postiz deployment guide for the bundled runtime, source archive and backup procedure.

Prepare a week you can review

Choose New draft to write a post with its source title, HTTPS URL and supporting excerpt, or use Prepare three-post week when you already have three reviewed paragraphs. For example, fictional Northline Roofing might supply separate paragraphs about inspection timing, drainage maintenance and records to keep after a storm, all supported by its own maintenance guide.

Weekly preparation preserves those paragraphs as three editable posts with source links, spaced two days apart. You can also enable Prepare weekly drafts in plugin settings and supply the source, page ID and paragraphs there. The scheduled worker prepares that week's drafts automatically, and you update the source material as your editorial plan changes.

Select the posts you want to publish and choose Review selected. The review shows each post's text, image, company page, date and time zone before you approve the exact batch. Calendar then gives you the retained schedule, and the background worker submits each post when its approved time arrives.

Follow the publication result

Open Results to see the provider's progress. An accepted submission means Postiz received the request; the published state includes the LinkedIn URL returned by the provider. Available metrics are refreshed daily, while unavailable engagement data stays explicitly unavailable.

If a connection fails after submission, the attempt retains an unknown outcome so the worker cannot silently send a duplicate. Inspect the organization's history in Postiz, enter the exact post ID in Results, and review the matching receipt before associating it with the attempt. That operation records the provider result without submitting another post.

You can cancel a schedule before dispatch. Disabling the plugin stops new draft preparation and submissions, while the history page preserves authorized reads and background receipt checks. After configuration changes, credential changes or missed schedules, edit the time and approve a fresh version so the worker has current authority.

Work through AI or MCP

Ask the assistant to inspect the social workspace, prepare a source-backed week, preview a draft change or propose a publication schedule. These operations use the same records and approval flow as the screens, so a conversational edit receives the same checks and receipts. Publication remains an exact human-approved action because it creates public content.

Excerpt preparation is deterministic and has no model charge. Ordinary AI conversations use your configured model and budget, while the bundled workers use hosting resources and connected providers can incur charges. Plugin developers can reuse the manifest's upstream repository, license, pinned revision and deployment-guide fields when packaging another open-source service.

Connect it to the rest of your work

Use a published Site Studio page as a source, or ask the assistant to find reviewed material through its existing authorized workspace knowledge and Drive tools. Give social preparation the source title, public URL and supporting excerpt, then review the public wording. Private documents do not become approved public content merely because the assistant can read them.

You can coordinate the post copy with an existing campaign, or review a suitable Opportunity Radar finding as editorial input. This version has no automatic Drive-to-social, website-publish-to-social or Radar-to-social trigger. It also does not enroll CRM contacts or calculate revenue attribution. Those extensions should use the existing feature services and retain source identities, permissions and approval checks.

The work engine already handles weekly drafts, approved publication times and receipt checks. The optional weekly automation reuses the configured source paragraphs until you change them. Use Work to inspect failed preparation; use Results to investigate an uncertain publication.

Extend the plugin

The Social Marketing extension guide maps the implementation and explains how to add a source trigger, another channel or shared reporting. Upstream Postiz support does not automatically enable a channel in Command Center: this version supports LinkedIn company pages, text and one image, with reviewed destination and receipt rules.

For another upstream project, follow the open-source service packaging guide. The repeatable package includes module metadata, a narrow tenant-aware adapter, native screens and AI tools, durable jobs, public and operator docs, deployment assets and verified recovery. Enabling a plugin does not provision its external service.

The service deployment keeps draft image URLs private, so use Social Marketing for image previews while upstream Postiz handles account setup. Operators can collect startup and recovery receipts through the deployment guide's isolated service verification before connecting a real company page.

What to check

Use the hardened service version required by Setup, then verify the host, LinkedIn application access, separate organizations, backup restoration and a real approved publication before activating a customer workspace. The full admin demo uses fictional session data, so use its screenshots to learn the workflow and real provider receipts to establish operational readiness. Check dates around daylight-saving changes, refresh source paragraphs regularly, and complete the internal pilot before offering the plugin to selected customers.

Install with the app

The forkable Docker package includes the app and Postiz runtime. Configure the app .env, set APP_HOST, and set SOCIAL_MARKETING_ENABLED=true before running npm run stack:up. Point the app hostname and its social subdomain to the same host. The package builds and connects the services; LinkedIn authorization and workspace connection remain setup steps. The repository deployment/README.md covers installation, updates and stopping without deleting data.