01
Native connections
Provider OAuth
Use the source-specific setup for enabled CRM, call-tracking, Google Ads, Meta Ads, analytics, and Slack connections.
Adscriptly integrations
Connect your ad stack with clear permissions.
Connect native providers, AI clients, Zapier, webhooks, lead forms, and reporting destinations. Every guide states the connection method, data path, and current boundary.
Four connection paths
Choose the connection path that matches your workflow.
Use native OAuth for supported providers, hosted MCP for compatible AI clients, webhook or Zapier for custom event routes, and read-only reporting for shared analysis.
02
Hosted MCP
AI clients
Connect Claude, ChatGPT, Claude Code, Cursor, and other compatible clients to one Adscriptly OAuth endpoint.
03
Webhooks & Zapier
Universal route
Receive a mapped event from any tool that can send a webhook or participate in a Zapier workflow.
04
Reporting delivery
Slack & analysis
Send configured agent updates to Slack and compare read-only account data in Adscriptly reports.
Priority workflows
Start with the integrations carrying the clearest demand.
Start with the most requested workflows, then confirm each guide's connection method, data path, and current limits.
01Hosted MCP
Google Ads to AI clients
Ask account-specific questions and run permissioned advertising workflows without placing Google Ads credentials inside the chat client.
02Hosted MCP
Meta Ads to AI clients
Give an AI client authenticated Meta Ads evidence without granting it campaign-management permission.
03Native Slack app
Google Ads to Slack
Give the team a shared place to ask account questions and receive scheduled advertising updates.
04Native connection
HubSpot to Google Ads
Help Google Ads distinguish a new contact from a qualified opportunity or closed deal.
05Webhook or Zapier
Klaviyo to Google Ads
Separate a lifecycle milestone or revenue event from a generic subscriber event before it reaches Google Ads.
06Webhook or Zapier
Facebook Lead Ads to Google Sheets
Give sales or operations a simple lead ledger without stripping away the paid-media context.
Integration directory
Find the workflow by app, outcome, or connection method.
Search all 30 guides by platform, business outcome, or connection method. Each guide explains its setup path and current boundaries.
30 workflows
Google Ads to AI clientsSearch demandAsk account-specific questions and run permissioned advertising workflows without placing Google Ads credentials inside the chat client.Hosted MCPAI & MCPMeta Ads to AI clientsSearch demandGive an AI client authenticated Meta Ads evidence without granting it campaign-management permission.Hosted MCPAI & MCPGoogle Ads to SlackGive the team a shared place to ask account questions and receive scheduled advertising updates.Native Slack appReporting & dataHubSpot to Google AdsSearch demandHelp Google Ads distinguish a new contact from a qualified opportunity or closed deal.Native connectionCRM & revenueKlaviyo to Google AdsSearch demandSeparate a lifecycle milestone or revenue event from a generic subscriber event before it reaches Google Ads.Webhook or ZapierLifecycle & ecommerceFacebook Lead Ads to Google SheetsSearch demandGive sales or operations a simple lead ledger without stripping away the paid-media context.Webhook or ZapierLead captureCallRail to Google AdsSearch demandOptimize toward calls that meet your business threshold instead of counting every ring as an equal result.Native connectionLead captureFacebook Lead Ads to Webhook or ZapierRoute Facebook leads to a mapped CRM, sheet, email, or sales system through one consistent, testable workflow.Webhook or ZapierLead captureGoogle Ads to ClaudeAsk Claude account-specific Google Ads questions with a visible permission boundary.Hosted MCPAI & MCPSalesforce to Google AdsSearch demandOptimize paid search toward qualified Salesforce lead outcomes instead of treating every captured lead as equal.Native connectionCRM & revenueFacebook Lead Ads to SalesforceSearch demandGive Salesforce users a lead record that still shows which Facebook form and ad produced it.Webhook or ZapierLead captureFacebook Lead Ads to HubSpotGive lifecycle and sales teams a HubSpot contact with the lead-source context needed for follow-up.Webhook or ZapierLead captureCRM to Google AdsSend qualified CRM events to Google Ads through a webhook or Zapier when no native Adscriptly connector is available.Webhook or ZapierCRM & revenueShopify to Google AdsSearch demandUse qualified Shopify order outcomes as Google Ads conversion signals. This route does not manage product feeds or Merchant Center.Webhook or ZapierLifecycle & ecommerceMeta Ads to OpenClawGive an OpenClaw workflow selected Meta Ads evidence while keeping the current Meta Ads connection read-only.Hosted MCPAI & MCPFacebook Lead Ads to ZapierUse Zapier for app coverage while keeping qualification and paid-media context visible in the handoff.ZapierLead captureFacebook Lead Ads to MailchimpMove eligible leads into lifecycle follow-up without treating every form submission as marketing consent.Webhook or ZapierLead captureMeta Ads + GA4 to Adscriptly reportsCreate one cross-channel brief while keeping Meta and GA4 metrics in their original systems.Connected account readsReporting & dataPipedrive to Google AdsHelp Google Ads distinguish a captured contact from a Pipedrive lead or deal outcome your team considers qualified.Native connectionCRM & revenueGoHighLevel to Google AdsRoute each client or location’s qualified GoHighLevel outcomes to the correct Google Ads account.Native connectionCRM & revenueZoho CRM to Google AdsOptimize paid search toward the Zoho lead statuses your team defines as qualified or converted.Native connectionCRM & revenueActiveCampaign to Google AdsHelp Google Ads distinguish a nurture event from the contact or deal milestone your team treats as qualified.Webhook or ZapierLifecycle & ecommerceCalendly to Google AdsOptimize toward selected booked meetings instead of counting every scheduling-page visit as equal.Webhook or ZapierLead captureHubSpot to Meta AdsSeparate a qualified HubSpot milestone from a raw lead event before it enters the Meta conversion path.Webhook or ZapierCRM & revenueInstapage to Google AdsSeparate a qualified landing-page response from a generic form submission in Google Ads.Webhook or ZapierLead captureKlaviyo to Meta AdsKeep a specific customer or revenue milestone distinct from a generic profile update before it enters the Meta event path.Webhook or ZapierLifecycle & ecommerceMailchimp to Google AdsUse a specific Mailchimp milestone instead of treating every audience update as a conversion.Webhook or ZapierLifecycle & ecommerceStripe to Google AdsConnect media optimization to a selected payment outcome rather than a page view or checkout start.Webhook or ZapierCRM & revenueWebhook to Google AdsUse one documented event contract for sources that can send the required webhook payload.WebhookReporting & dataZapier to Google AdsConnect supported Zapier apps while keeping the qualification rule and Google Ads destination visible.ZapierReporting & data
Platform permissions
What Adscriptly can read or change in connected platforms.
01
Google Ads
Account reads + separately scoped writes
Discover accessible accounts, analyze account data, and use supported write tools only through a separate scope and approval boundary.
02
Meta Ads
ads_read
Read accessible ad accounts and aggregate account performance. The current Meta Ads connection does not request campaign-management permission.
03
Google Analytics 4
analytics.readonly
Read aggregate acquisition and conversion reporting for a property selected by the authenticated user.
04
Google Tag Manager
tagmanager.edit.containers, tagmanager.edit.containerversions, tagmanager.publish
Create or update tags in a selected container. Publishing requires a separate container-specific confirmation.
05
Slack
app_mentions:read, commands, chat:write, mcp:connect
Handle explicit slash commands and @Adscriptly mentions, deliver configured notifications, and avoid broad workspace message-history access.
Control and removal
Disconnect without contacting sales.
Disconnecting in Settings stops future Adscriptly API access. Users can also revoke access directly with the provider.
Revocation and deletion are different. Follow the public deletion instructions to remove retained copies after revoking a provider.
