ReleaseWPChangeSync 2.0 is here →
Docs/Integrations

Integrations

Understand the integration registry that powers selective exports, imports, workflows, and library sections.
Updated June 2026·WPChangeSync 2.0

Integration registry

WPChangeSync discovers syncable areas from JSON manifests in the integration catalog. Version 2.0 includes 39 manifests across Bricks core, WordPress core content, Gutenberg, field plugins, CSS frameworks, and Bricks ecosystem plugins.

Each manifest describes how an integration should appear in the Library, whether it can be used in workflows, which handler owns the data, where files are stored, and which conflict defaults should be used.

Looking for a specific plugin or theme? Browse the full integration directory, every supported integration, searchable, plus the ones you can add yourself.

Current integration categories

CategoryIncluded manifestsTypical use
Bricks coreTemplates, components, settings, global classes, theme styles, variables, colors, custom CSS/code, custom icons, icon fonts, fonts, breakpoints, sidebars, typography, element defaults, pseudo classes, global elements, global queries, element manager, style manager, Adobe fonts.Move Bricks design-system and builder configuration between environments.
WordPress corePosts, pages, media, menus, widgets, categories, tags.Sync site content and operational content structures without database dumps.
BuildersGutenberg.Support block-editor content workflows on non-Bricks sites.
FieldsACF, ACF Post Types, ACF Taxonomies, Meta Box, ACPT.Move field definitions, CPT/taxonomy definitions, and related configuration.
CSS frameworksAutomatic.css, Core Framework.Carry framework configuration alongside builder and WordPress settings.
Bricks pluginsAdvanced Themer, Bricksforge.Sync plugin-owned builder ecosystem settings where supported.

What a manifest controls

  • Label and grouping: how the integration appears in the Library and workflow editor.
  • Handler: whether data is handled as options, arrays, CPTs, media, taxonomy terms, widgets, menus, or custom tables.
  • Storage path and filenames: how exported JSON is organized for Git-friendly review.
  • Selective support: whether individual items can be listed, selected, exported, pushed, or imported.
  • Preview and workflow visibility: whether the integration participates in dependency previews and workflow steps.
  • Safety defaults: default conflict handling, excluded option patterns, and plugin-specific safeguards.

Selective sync behavior

Integrations with listable items can expose export/import actions for a single item, selected items, or all items. Library sections then provide actions such as Export, Import, Push Selected, and workflow run controls where the handler supports them.

Some integrations intentionally do not support selective operations because their data is a coupled option set or a plugin-owned configuration bundle. In those cases, sync the whole integration and use dry-runs, backups, and conflict strategies before applying changes.

Non-Bricks sites

WPChangeSync 2.0 is builder-agnostic. When Bricks is not installed, Bricks-specific integrations are skipped gracefully and WordPress, Gutenberg, fields, remotes, workflows, audit, and storage workflows remain available where supported.

For a practical setup path, see the Non-Bricks WordPress Workflow guide.

Plugin not listed? Add it yourself

WPChangeSync isn’t limited to the integrations above. With Custom Integrations you can build a no-code data source from almost any plugin’s options, tables, post types, and taxonomies, and sync it like everything else. See the no-code guide.