Integration
Connect Privy and wethod
When New Contact fires in Privy, your agent runs Create a contact in wethod, or New Client in wethod to Find Contact in Privy. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Privy and wethod to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Privy and wethod can do together
From Privy to wethod
When New Contact in Privy
then Create a contact in wethod
When New Order in Privy
then Create an invoice in wethod
From wethod to Privy
When New Client in wethod
then Find Contact in Privy
When New Contact in wethod
then Check Coupon Code in Privy
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Privy and wethod
Triggers and actions 9 triggers · 83 actions
Trigger
New ContactTriggers when a new contact is added to your Privy account.
Trigger
New OrderTriggers when a new order is recorded in your Privy account.
Action
Check Coupon CodeCheck a coupon code. Check whether an individual code from a Shopify or BigCommerce pool has been redeemed, read live from the connected store's per-code usage counter (Privy stores no redemption events).
Action
Delete ContactDelete a contact by ID. Soft-delete a contact identified by its unique `id`.
Action
Find ContactList contacts. Retrieve a paginated list of contacts, most recently created first. Optionally filter by email, phone number, or consent status.
Action
Get AccountGet account. Retrieve information about the Privy account associated with the API token.
Action
Get Business Summary ReportGet business report summary. The business-level performance rollup for a period: signups, new subscribers, attributed revenue and orders, engagement rates, and business-wide order and revenue totals for context. Pass `compare=previous_period` to add previous-period values and typed change deltas to every metric.
Action
Get CouponGet a coupon. Retrieve a single coupon pool by its identifier — the list rows' inventory and health, plus `usage_count`, the connected store's pool-wide redemption counter read live.
Action
Get Display ReportGet display performance. The full performance stat set for one display over a period, including average order value and, when the display has run an A/B test, per-variation participants, conversions, and conversion rates.
Action
Get FlowGet a flow. Retrieve a single flow by its identifier, including its full configuration: re-entry behavior, flow filters, effective exit behavior, a server-generated behavior summary, and the node tree — each step's configuration (`data`) plus the branch graph, with split conditions and the nodes on each branch.
Action
Get ImportGet a contact import. Retrieve a single contact import — the same row `/v1/imports` lists for it.
Action
Get ProductGet a product. Retrieve a single product from your connected store's catalog by its store product id.
Action
Get Product CollectionGet a product collection. Retrieve one collection (Shopify) or category (BigCommerce) of your connected store by its store id, the `id` a `purchase_history` segment condition's `collection` filter holds.
Action
Get SegmentGet a segment. Retrieve a single segment by its identifier. The members themselves are `/v1/segments/{id}/contacts`. A campaign's `audience` segment ids resolve here when the segment was saved to the account. There is no per-segment performance report anywhere in the API.
Action
Get Segment CountsReturns how many contacts a segment reaches today: total, mailable and textable counts.
Action
Get TagGet a tag. Retrieve a single tag by its prefixed id — the same row `/v1/tags` lists for it. This is how to name the `tag_…` and `stag_…` ids that appear in a flow's condition tree.
Action
List Campaign ReportsList campaign performance. Every message campaign **sent in the period**, ranked by attributed revenue, each row carrying the full channel stat block (delivery, engagement, unsubscribes, attribution) scoped to the same period — so period comparisons need no per-campaign detail calls. Zero-revenue sends are listed too, ranked after the revenue rows; at most 100 campaigns are ranked, and a send with
Action
List CampaignsList campaigns. Retrieve a paginated list of your message campaigns, newest first.
Action
List Collection ProductsList a collection's products. Retrieve the products in one collection (Shopify) or category (BigCommerce) of your connected store, in the same shape as `/v1/products`.
Action
List Contact ActivityList a contact's activity. Retrieve the contact's activity timeline — signups, email and SMS sends, opens and clicks, orders, checkouts, tag changes — newest first. This is the same record the Privy dashboard's contact page shows, so "why did this contact get X?" can be answered from the API alone: find the send, the signup that triggered it, and the display or campaign each traces to.
Action
List CouponsList coupons. Retrieve a paginated list of your coupon pools with their code inventory and health status.
Action
List Display ReportsList display performance. Rank your displays by performance over a period — signups by default, or any of the documented sort keys. Displays whose value for the chosen sort key is zero are left out entirely, and ranking stops at 50 displays, which also caps the reported `total_count`. Use `/v1/reports/displays/{display_id}` for one display's full stat set, including average order value and A/B tes
Action
List DisplaysList displays. Retrieve a paginated list of your on-site displays, newest first. Archived displays are excluded by default — pass `status=archived` to list them.
Action
List Email TemplatesList email templates. The templates an email draft may start from: the account's own saved newsletter templates, listed first, and then Privy's gallery. Names and facets only; the design and HTML stay on the server, and a template is branded for the account only when a draft uses it. Templates with product blocks are offered only to an account with a connected catalog store. Templates whose produc
Action
List Flow ReportsList flow performance. Rank your flows by performance over a period — best performers first, remaining flows by recency. Each row combines email and SMS stats across the flow's message steps. Use `/v1/reports/flows/{flow_id}` for one flow's report including the per-node message breakdown.
Action
List FlowsList flows. Retrieve a paginated list of your automation flows, including each flow's trigger and steps.
Action
List ImportsList contact imports. Retrieve a paginated list of your contact imports — CSV uploads and connected-provider syncs — most recently requested first. Each row mirrors the dashboard's import history: type, processing status, contact counts, who requested it, when, and its review status.
Action
List OrdersList orders. Retrieve a paginated list of your orders across every source (Shopify, BigCommerce, Weebly, Wix, and orders reported via this API), most recently created first.
Action
List Product CollectionsList product collections. Retrieve the collections of your connected store, proxied live from the store's API: Shopify collections, or BigCommerce categories.
Action
List Product Collections For ProductList a product's collections. Retrieve the collections (Shopify) or categories (BigCommerce) one product of your connected store belongs to, by its store product id.
Action
List ProductsList products. Retrieve the product catalog of your connected store (Shopify or BigCommerce), proxied live from the store's API.
Action
List Segment ContactsList a segment's contacts. Retrieve the segment's members as a paginated list of contacts, in the same shape as the Contacts API, most recently created first.
Action
List SegmentsList segments. Retrieve a paginated list of your customer segments with their mailable/textable member counts.
Action
List TagsList tags. Retrieve a paginated list of the account's contact tags, ordered by name. Tag names are lower-cased and trimmed. Some older tags have not been merged yet, so the same name can appear on more than one row, each with its own id.
Action
List Top Products ReportList top products. Retrieve your store's top products ranked by views or sales over a 30, 60, or 90 day window, or all-time where the platform supports it.
Trigger
New ClientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Trigger
New ContactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Trigger
New InvoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Trigger
New PersonHere the dedicated support page.
Trigger
New ProjectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Trigger
Sent InvoiceTriggers when an invoice is in sent status.
Trigger
Updated ProjectTriggers when a project is created or updated.
Action
Archive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Create a clientRequired permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.
Action
Create a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Create an invoiceRequired permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.
Action
Create a personCreates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/
Action
Create a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Create a projectRequired permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met
Action
Create a project statusRequired permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.
Action
Create a timesheetRequired permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Delete a clientRequired permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.
Action
Delete a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Delete an invoiceRequired permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.
Action
Delete a person allocationRequired permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He
Action
Delete a projectRequired permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.
Action
Delete a timesheetRequired permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.
Action
Find ClientFinds the first client whose name matches the search text.
Action
Find PersonFinds the first person whose name or email matches the search text.
Action
Get a budgetRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
Get a clientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
Get a contactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
Get an expenseRequired permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.
Action
Get an invoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.
Action
Get a personHere the dedicated support page.
Action
Get a projectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
Get a stream:::warning Requires **Streams** to be enabled in company settings. :::
Action
Get the authenticated personReturns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.
Action
List budgetsRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
List business unitsRequired permissions: - **settings.company**: allows view of company business units.
Action
List clientsRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
List contactsRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
List expensesRequired permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.
Action
List invoicesRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Action
List job titlesRequired permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.
Action
List people allocationsRequired permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.
Action
List personsHere the dedicated support page.
Action
List projectsThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
List project statusesRequired permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.
Action
List project typesList project types
Action
List streams:::warning Requires **Streams** to be enabled in company settings. :::
Action
List timesheetsRequired permissions: - **timetracking.view** Here the dedicated support page.
Action
Set an invoice as paidRequired permissions: - **invoices.edit_sent**: allows setting invoices as paid.
Action
Set an invoice as unpaidRequired permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.
Action
Unarchive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Update a clientRequired permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.
Action
Update a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Update an invoiceRequired permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.
Action
Update a personRequired permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.
Action
Update a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Update a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].
Action
Update a timesheetRequired permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Privy
Privy to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Privy to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Privy to StripeStripe is a payment processing platform for online businesses.
Privy to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Privy to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Privy to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into wethod
HubSpot to wethodHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to wethodSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to wethodSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to wethodGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to wethodGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to wethodGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Privy and wethod, answered
What can start an automation from Privy?
Any of Privy's 2 triggers in the catalog, including New Contact and New Order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in wethod when something happens in Privy?
Any of wethod's 50 actions, including Create a client, Create a contact, Create an invoice and Create a person. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from wethod to Privy?
Yes. When something happens in wethod, your agent can act in Privy too. This page covers both directions: wethod's triggers and Privy's actions are listed here as well.
Do I have to build a connector for Privy or wethod?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Privy and wethod without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.