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.76 connectors with pull and push capability (live snapshot, 2026-08-03)
76 connectors with pull and push capability (live snapshot, 2026-08-03)
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:- Read the catalog and require
capabilities.push: true. - Resolve the connected account’s writable objects, fields, and mutation modes.
- Produce a structured plan or dry run.
- Require explicit approval for consequential writes.
- Execute with an idempotency key and retain an audit record.
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.