Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.socializioz.com/llms.txt

Use this file to discover all available pages before exploring further.

Socializioz connects to external tools and receives real-time updates from social platforms through webhooks and integrations. This page explains the available integrations and how they work.

Zapier integration

Socializioz can send notifications to Zapier when certain events happen in your workspace. This lets you build automated workflows that connect Socializioz to thousands of other apps — for example, logging scheduled posts to a Google Sheet, sending a Slack message when a post is published, or updating a project management tool when content is approved.

How it works

When you schedule a post in Socializioz, a webhook notification is sent to your connected Zapier workflow (called a “Zap”). The notification includes details about the post such as the platform, caption, scheduled time, and associated campaign.

What triggers are available

TriggerWhen it fires
Post scheduledA post is added to the schedule or rescheduled to a new time
Additional triggers (post published, post failed, campaign created) are planned for future releases. Currently, the post-scheduled event is the available Zapier trigger.

Setting up a Zapier workflow

1

Create a Zap in Zapier

Log in to your Zapier account and create a new Zap. Choose Webhooks by Zapier as the trigger app and select Catch Hook as the trigger event.
2

Copy the webhook URL

Zapier generates a unique webhook URL for your Zap. Copy this URL.
3

Configure the webhook in Socializioz

Contact support to register your Zapier webhook URL with your workspace. The support team will configure the endpoint for your account.
4

Test the connection

Schedule a test post in Socializioz. Zapier should receive the webhook payload within a few seconds. Verify the data in Zapier’s test step, then continue building your Zap.
5

Add actions

Add one or more actions to your Zap — for example, create a row in Google Sheets, send a Slack notification, or update a Trello card. Map the Socializioz webhook fields to your action fields.

Webhook payload

The Zapier webhook includes the following data:
FieldDescription
post_idThe unique identifier of the scheduled post
platformThe target social platform (e.g., instagram, facebook, tiktok)
captionThe post caption text
scheduled_timeThe date and time the post is scheduled to publish (UTC)
campaign_idThe associated campaign ID, if any
workspace_idYour workspace identifier
Example payload:
{
  "post_id": "post_abc123",
  "platform": "instagram",
  "caption": "Summer sale starts today! #sale #summer",
  "scheduled_time": "2026-04-20T10:00:00Z",
  "campaign_id": "camp_xyz789",
  "workspace_id": "ws_def456"
}
The campaign_id field is null when the post is not assigned to a campaign. All timestamps are in UTC.
Zapier integration requires manual setup by the Socializioz support team — there is no self-service configuration. Contact support with your Zapier webhook URL to get started. Available on Professional and Enterprise plans.

Webhook delivery and retries

Socializioz sends webhook payloads to Zapier as a single HTTP POST request. If the delivery fails (for example, due to a network timeout or Zapier downtime), the webhook is not automatically retried. Failed deliveries are lost.
Zapier webhooks have no retry mechanism. If a webhook delivery fails, the event is not re-sent. Monitor the activity log for “Post scheduled” entries and compare them against your Zapier task history to catch any missed events. Consider building a reconciliation check in your Zap that periodically verifies recent posts.

Platform webhooks

Socializioz automatically receives webhook notifications from connected social platforms. These keep your workspace data in sync without manual refreshing.

How platform webhooks work

When you connect a social account, Socializioz registers to receive real-time notifications from that platform’s API. When something happens on the platform — for example, someone comments on your post or your video finishes processing — the platform sends a webhook to Socializioz, which updates your workspace data automatically.

What platforms send webhooks

PlatformEvents received
FacebookNew comments on posts, engagement updates, page activity
InstagramNew comments, mentions, story replies, engagement updates
TikTokVideo upload status changes, publish confirmations, processing errors
X and LinkedIn do not currently support real-time webhooks. Data from these platforms is synced periodically (approximately every few minutes). Engagement metrics and comments from X and LinkedIn may take longer to appear in your workspace compared to Facebook and Instagram. Telegram and WhatsApp integrations are coming soon and are not yet sending webhook events. See connecting accounts for the latest platform availability.

Where webhook events appear

Webhook events are logged in the activity log as Webhook received entries. You do not need to configure or manage these webhooks — they are set up automatically when you connect an account and removed when you disconnect. Webhook-triggered updates include:
If you notice that comments or engagement data are not updating, check the activity log for recent webhook events. Missing webhook events may indicate a connection issue — try reconnecting the account.

MCP tool integration

Socializioz MCP is a free integration for authenticated users. It connects a user workspace to ChatGPT and other MCP-compatible assistants for profile, account, draft, and scheduling workflows. For the public overview, see socializioz.com/mcp. For setup details and the correct endpoints, see Socializioz MCP.
Socializioz MCP (workspace connection) is free for authenticated users. Enterprise custom/private MCP tools are separate and only apply to private company/internal systems connected through Socializioz AI Chat.

What Socializioz MCP enables

With Socializioz MCP, assistants can perform authenticated workspace actions including:
  • Get user profile
  • List connected accounts
  • Create draft post
  • List scheduled posts
  • Schedule post
  • Reschedule post
  • Cancel scheduled post

Setting up MCP

Use the Socializioz MCP guide for the endpoint URLs, prompts, security notes, and troubleshooting steps.

MCP limitations

  • The first release focuses on safe publishing workflows.
  • It does not yet include analytics, inbox replies, media generation, billing, team permissions, or full account management via MCP.

API access

Enterprise plans include API access for programmatic interaction with your Socializioz workspace. The API lets you integrate Socializioz into your existing toolchains, build custom dashboards, or automate repetitive tasks.
API access is an Enterprise-only feature. Contact support or your dedicated account manager to receive your API credentials and endpoint documentation.
This Enterprise API feature is separate from Socializioz MCP. Socializioz MCP is free for authenticated users and is used to connect MCP-compatible assistants to a user workspace.

What you can do with the API

CapabilityDescription
Post managementCreate, schedule, update, and retrieve posts programmatically
Campaign dataRead campaign details, content plans, and performance metrics
Analytics exportPull engagement metrics, audience data, and performance reports
Account statusCheck connection health and token status for all linked accounts
Media uploadUpload assets to the media library via API

Getting started with the API

1

Request API credentials

Contact support to enable API access for your Enterprise workspace. You will receive an API key and endpoint base URL.
2

Authenticate requests

Include your API key in the Authorization header of every request. All API requests must use HTTPS.
3

Explore available endpoints

Your account manager will provide endpoint documentation specific to your workspace configuration.
Keep your API key secret. Do not expose it in client-side code or public repositories. Rotate your key immediately if you suspect it has been compromised.

Troubleshooting

ProblemCauseFix
Zapier is not receiving webhooksThe webhook URL may not be registered correctlyContact support to verify your webhook configuration
Webhook payload is missing fieldsSome fields are only populated when available (e.g., campaign_id is empty if the post is not assigned to a campaign)Check the field list above and ensure the post has the expected data
Comments are not appearing in real timePlatform webhook delivery can be delayed during high-traffic periodsWait a few minutes, then pull to refresh on the comments page. If comments are consistently missing, reconnect the affected account
TikTok status not updatingTikTok webhook delivery depends on their processing queueCheck the activity log for TikTok webhook events. If none appear after 30 minutes, try reconnecting your TikTok account
Activity log shows “Webhook received” but data did not updateThe webhook was received but the data may still be processingRefresh the relevant page (comments, analytics, or schedule). If the issue persists, contact support
Last modified on May 16, 2026