Zoho Social

Overview

The Zoho Social source syncs social account, channel, post, and metric data into Daspire-managed destinations. It is implemented as a Daspire-owned connector and is exposed through the Control API source workflow, not through a customer-facing runtime or Airbyte endpoint.

Use the Control API base path:

/api/control/v1

Create and manage Zoho Social sources through:

• GET /connectors
• GET /connectors/{connector_id}/spec
• POST /credentials/source/oauth/start
• POST /credentials/source/oauth/callback
• POST /sources
• POST /sources/check_connection

connector_id, source_id, and credential_handle are the primary product identifiers. Legacy runtime ids such as source:85124378-057c-4755-b3bb-b9e614a229be are accepted only for saved configuration compatibility.

Prerequisites

• A Zoho Social account with administrator access to the required Portal, Brand, and Channels.
• Zoho Social API access enabled for the account and region.
• A Daspire OAuth credential handle returned by the Zoho Social source OAuth flow.
• OAuth scopes confirmed for the customer tenant. The alpha consent flow requests read-only Zoho Social post, channel, and report scopes.
• Portal ID and at least one Brand ID.
• Optional Channel IDs when the sync should be limited to specific connected social channels.

Zoho's public REST API catalog does not currently list Zoho Social as a broadly documented public API, while Zoho Social itself supports publishing, monitoring, and analytics for connected social channels. Daspire therefore treats the connector as alpha and fails closed when the Social API is unavailable for the customer's account or region.

References:

• Zoho REST API catalog
• Zoho Social overview
• Zoho Social channel connection guide

Configuration

Field	Required	Notes
credential_handle	Yes	Returned by the Daspire source OAuth callback. Secrets and provider tokens are not returned by the Control API.
portal_id	Yes	Zoho Social Portal ID.
brand_ids	Yes	One or more Zoho Social Brand IDs to read.
channel_ids	No	Limits reads to selected channels. Leave blank to read all channels visible to each brand.
start_date	Yes	First date for post and metric reads.
end_date	No	Last date for post and metric reads. Defaults to the current date.
page_size	No	Request page size, default 100, maximum 200.

Example source create payload:

{
  "connector_id": "conn_zoho_social_product_id",
  "name": "Zoho Social - Brand A",
  "connectionConfiguration": {
    "credential_handle": "cred_source_oauth_zoho_social",
    "portal_id": "123456789",
    "brand_ids": ["987654321"],
    "start_date": "2024-01-01"
  }
}

Supported Streams

• portals
• brands
• channels
• posts
• post_metrics
• account_metrics

The connector preserves provider response fields with schema drift support. Customer-safe context fields such as portal_id, brand_id, channel_id, metric_date, start_date, and end_date are added where applicable.

Expected metrics include impressions, reach, engagement, clicks, followers, likes, comments, and shares when Zoho Social returns those fields for the account, channel, or post. Unsupported provider fields are omitted or left null; raw provider fields remain traceable in the stream record.

Incremental and Sync Behavior

Post and metric streams read by configured date window. Metrics are sliced by day so a failed run can retry a bounded date range. The connector does not change existing Daspire schedules, selected catalogs, state, billing, usage accounting, or warehouse naming behavior.

Migration and Rollback

Adding Zoho Social does not migrate customer connections, does not reuse the Zoho Desk connector, and does not change any source definition id for existing connectors. Existing source, destination, pipeline, job, catalog, schedule, billing, usage, and _daspire_* warehouse names are preserved.

Rollback is limited to disabling or removing the new Zoho Social source definition or connector image tag. No customer connection or connector migration is performed automatically.

Limitations

• API availability depends on Zoho enabling Social API access for the customer's account and data center region.
• Zoho's channel-level API limitations may vary by social network. For example, some Instagram story statistics depend on how the Instagram channel is connected in Zoho Social.
• OAuth raw config, provider tokens, Docker image metadata, runtime ids, internal paths, and raw stack traces are never returned in default customer responses.