Skip to Content
PlugSync documentation preview build
ReferenceConfig V3Config V3 schema reference

Config V3 schema reference

ConnectorConfigV3 is the source of truth for a Plugsync connector’s configuration. This reference documents every field, the validators that will reject your config, and the workflow that promotes a draft to the live worker pool.

If you are a partner, plugin developer, or self-service customer authoring a connector config without access to the backend repository, this reference plus the two examples in _examples/ is meant to be everything you need.

Top-level shape

{ "version": "3.0", "entities": [], "flows": [], "settings": {} }
PageWhat’s there
connector.mdTop-level fields (version, entities, flows, settings).
entities.mdEntityV3, EntitySchemaSpec, IdentityConfig, FieldMapping.
flows.mdFlowV3 + the dispatch model.
step-actions.mdThe 10-action step DSL.
simple-vs-federated.mdThe two entity modes and when to pick which.
draft-publish.mdThe draft->publish workflow with dashboard screenshots.
examples.mdTwo narrated walkthroughs of complete configs.
_examples/Two copy-pasteable JSON files plus the CI validator.

Prerequisites

Before any of this is useful:

  1. You have a Plugsync org and an authenticated user.
  2. You’ve completed the HubSpot OAuth flow once (so a HubSpot credential exists in your org).
  3. You’ve created a connector via the dashboard or POST /api/connectors.

The connector starts with an empty draft. You author the config you want, review the diff, and publish.

First config in 30 seconds

Copy _examples/compass-light.json, substitute your actual source name where it says compass_inbound, and:

curl -X PATCH https://app.plugsync.com/api/connectors/<id>/draft \ -H "Authorization: Bearer <token>" \ -H "Content-Type: application/json" \ -d @compass-light.json

Then open the connector workspace in the dashboard, click “Review changes”, and click “Publish v1”. Your connector is now live.

Out of scope

This reference deliberately does not cover:

  • Event flow manifest authoring deep-dive (compilation, dedupe). See #ENG-57.
  • Plugin authoring (Lambda + TypeScript SDK). See #ENG-58 and #190.
  • v2 schema and v2->v3 migration. v2 is deprecated.
  • DynamoDB replica internals. See ADR-0014.
Last updated on