Converly

Get the full detail of one flow — its trigger, actions, and status. Pass the flow_id from list_flows.

get_flow

Get the account's current Converly subscription: plan, status, trial state, and usage limits. Use this to check whether the account is on a trial, active, or past due.

get_subscription

Get the tracking snippet (a small script tag) the user needs to add to their website so Converly can track conversions, plus the site_key. Give this to the user whenever get_install_status isn't "confirmed" — without it on the site, published flows capture nothing. Pass the site_id from list_sites.

get_install_snippet

For a CONNECTED form platform (a requires_connection provider from list_trigger_types), list the filter fields it supports and the account's REAL values for each — e.g. the actual Typeform forms or Calendly event types, with ids and names. Use this after connecting to offer the user a specific form/event type, then pass the choice as trigger_config.conditions on create_flow/update_flow, e.g. {"form": {"ids": ["abc"], "names": ["Demo Request"]}}. Values come live from the platform; never invent filter values that aren't in this list.

list_trigger_filter_options

List the ad platforms / destination types Converly can send conversions to (e.g. Google Ads, Meta, LinkedIn, TikTok), with how each one connects. Each entry has connection_types: a NON-empty array (e.g. oauth/paste_token) means the destination must be connected first via connect_destination; an EMPTY array means it's a browser-side pixel destination that needs no connect step — read its fields from list_action_types and write the action directly.

list_destination_types

List the ad platforms / destinations connected to the account (e.g. Google Ads, Meta) and their connection status. These are where conversion events get sent when a flow fires.

list_destinations

List conversion flows in the account. A flow = a trigger (e.g. a form submission) plus the conversion actions it fires to ad platforms. Optionally filter to one site by passing its site_id (the prefixed id from list_sites, e.g. "site_abc").

list_flows

List the conversion actions configured on a connected destination (e.g. the conversion actions in a Google Ads account). Use this to find the right conversion to reference when setting up a flow's action. Pass the destination_id from list_destinations. For Google Ads, pick an entry whose usable field is true. An entry with usable false cannot receive conversions from Converly (its reason field says why, and flow writes that pick it are refused). Brand-new Google Ads accounts often contain ONLY unusable Google-created actions, so when nothing usable is listed, offer create_conversion instead. A missing usable field means no verdict.

list_conversions

List recent conversion events Converly captured (the live tracking log): each shows the flow, destination, status (e.g. converted / failed), and time. Use this to check whether conversions are being tracked, to CONFIRM whether a conversion matching an email exists and how it was delivered (email filter — you supply an address you already know; visitor PII is NOT returned in the results), or to list failures (status filter). Filters: site_id, flow_id, email (exact match), status, occurred_after / occurred_before (ISO timestamps). This returns a BOUNDED SNAPSHOT of the most recent matching events (up to `limit`); `has_more: true` means older events exist beyond the window — narrow with the filters (especially email / occurred_after / occurred_before) rather than paging. IMPORTANT: when the response has `complete: false`, the search was truncated at the recent window, so an empty or short result does NOT prove no matching conversion exists — do not tell the user 'no conversion was found'; say the recent window has none and offer to narrow by date. Not the full archive.

list_events

List the trigger types Converly supports — the kinds of events that can start a flow (e.g. form submissions, meeting booked) and the form/tool providers for each. Use this to find the trigger integrationId to pass to create_flow's trigger_config. Providers marked requires_connection: true (form platforms like Typeform) must be connected first with connect_trigger_source; pass site_id to see each one's live connection state for that site. Filtering: most triggers fire on ALL pages or only specific pages (trigger_config.pageFilter and pages). Connected form platforms instead support narrowing to a specific form or event type via trigger_config.conditions — discover the real options with list_trigger_filter_options. Do not offer any other filtering (CSS selector, product, or similar).

list_trigger_types

List the websites in the connected Converly account (returns each site's id, name, and domain). Use this first to discover which site a flow or destination belongs to.

list_sites

Publish a flow so it goes live and starts tracking conversions. This pushes the account's configuration to Converly's CDN, so the change takes effect on the customer's website. The flow must have a trigger and at least one action, and the account must be in good standing. (You can stop future tracking with unpublish_flow, but conversions already delivered while the flow was live cannot be recalled.) Pass the flow_id from list_flows or create_flow. Note that publishing alone captures nothing unless the Converly snippet is installed on the website. The result may include install_status; if it is absent, call get_install_status. If its detection is "never_seen", give the user the snippet from get_install_snippet and wait for them to confirm it is installed before suggesting any test.

publish_flow

Fire a single conversion to a destination to verify a flow's action is wired up, without waiting for a real form submission. It tests the DESTINATION-FORWARDING path only: it does NOT prove the snippet is installed, the origin is authorized, or that a real submission would be captured, and it does NOT appear in list_events (that's the real capture log). Pass the action to test by action_id (from get_flow's actions_config; it must belong to the flow) — the action's STORED config is used, the config you pass is ignored. For Meta pass meta_test_event_code (Test Events tab); for Reddit/TikTok pass reddit_test_id / tiktok_test_event_code. WITHOUT a valid sandbox code, server-side ad destinations (google-ads, chatgpt-ads, linkedin-ads, google-analytics, and meta/reddit/tiktok) create a REAL conversion in campaign reporting, so the call is REFUSED unless you set allow_real_conversion:true — confirm with the user first.

send_test_event

Unpublish (pause) a live flow so it stops tracking conversions, while keeping its configuration so it can be re-published later. This pushes the updated configuration to Converly's CDN. Pass the flow_id from list_flows.

unpublish_flow

Update a flow's name, description, trigger, or actions. (To take a flow live or pause it, use publish_flow / unpublish_flow instead — status isn't changed here.) IMPORTANT: updating a PUBLISHED flow does NOT change what runs on the website — the result's publication_state turns "pending" and the site keeps running the previous version until publish_flow is called. Pass at least one field to change. The flow keeps its current values for anything you omit.

update_flow

Update a site's name, website address (domain), or timezone. Setting the domain matters most: Converly rejects conversions from websites it doesn't recognize, so a site with no domain captures NOTHING even with a published flow and the snippet installed. Whenever list_sites shows domain null, ask the user for their website URL and set it here. Pass the site_id from list_sites and at least one field to change.

update_site

Check whether a flow is ready to publish, without publishing it. Returns whether it's valid and a list of any problems (e.g. missing trigger or action) so you can fix them before calling publish_flow. Pass the flow_id from list_flows.

validate_flow