Skip to main content
The connector catalog exposes data direction explicitly. Use it to decide whether a connector is only a memory source or can also participate in a write-back workflow.
push: true is capability discovery, not a write operation or permission grant. The public Conare API does not currently expose a generic connector mutation endpoint. POST /api/v1/connectors/sync always pulls data into Conare.

Discover push-capable connectors

Query the catalog instead of maintaining an allowlist. It is fetched from the connector plane, so newly supported destinations appear without a Conare release.
Attio currently returns:
As of August 3, 2026, 76 of 205 connectors returned by the public catalog also report write-back support. The API response is always the source of truth.
Affinity, Airtable, Amplemarket, Amplitude, Apollo.io, Attio, AWS Athena, Azure Blob Storage, Azure SQL, ClickHouse, Cloudflare R2, Databricks, DealCloud, Dialpad, Facebook Ads, Freshdesk, Front, Gainsight CS, Gong, Google Ads, Google BigQuery, Google Cloud MySQL, Google Cloud PostgreSQL, Google Cloud Storage, Google Sheets, Harmonic, HeyReach, HubSpot, Instantly, Intercom, Iterable, Klaviyo, Kustomer, LinkedIn Ads, Marketo, Microsoft Ads, Microsoft SharePoint Excel, Microsoft SQL Server, MongoDB, MotherDuck, MySQL, Neon, NetSuite, Northbeam, Outreach, Pardot, Pipedrive, Plain, PlanetScale Vitess, Podscribe, PostgreSQL, PredictLeads, Productboard, Pylon, QuickBooks, Reddit Ads, Redshift, Redshift Serverless, Reply, S3, Salesbricks, Salesforce, Salesloft, ScyllaDB, Smartlead.ai, Smartsheet, Snowflake, Sprig, Stripe, Supabase, Tigris, TikTok Ads, UserVoice, Wavelength, Zendesk Support, monday.com

What this means in practice

push: true does not imply that every action offered by the provider is available. In particular, it does not bypass provider permissions, identify writable objects, choose between draft and send, or execute an action by itself.

Building an action layer

A safe company-brain action flow should:
  1. Read the catalog and require capabilities.push: true.
  2. Resolve the connected account’s writable objects, fields, and mutation modes.
  3. Produce a structured plan or dry run.
  4. Require explicit approval for consequential writes.
  5. Execute with an idempotency key and retain an audit record.
Until Conare publishes a connector mutation endpoint, use the catalog for capability-aware UI and planning; do not present push: true as an executable Conare API action. See List the source catalog for the response schema and Trigger a sync for the pull-only sync operation.