Integration

YCloud integration

YCloud is an official Meta WhatsApp Business Solution Provider that also sends SMS, email and voice codes. Its API sends WhatsApp template, text, media, interactive and reaction messages (queued or synchronous), uploads media and reads message status; manages templates, Flows, groups, blocked users, business accounts and phone number profiles; sends Facebook Messenger text replies, SMS, email and voice codes and runs OTP verifications; manages contacts, notes, custom events, unsubscribers and webhook endpoints; reads the balance; and configures the Meta Business Agent (settings, knowledge, skills, evaluations). Every send reaches real people and is billed. Not exposed: WebRTC call signaling (connect, pre-accept, accept), Meta Business Agent connectors and connector tools (they hold third-party credentials) and webhook secret rotation; webhook signing secrets are withheld from every answer. Authentication is the account API key (YCloud dashboard, Developers, API key) or a custom app key (yc_ak_...), sent raw in the X-API-Key header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in YCloud.Built from the 145 YCloud tools below, on the connection you add once.

What you can do with YCloud

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Whatsapp group, 8 operations

  • create_groupCreate groupPOSTAgents: ask firstCreates an invitation-only WhatsApp group on a business phone number, with a subject, optional description and join mode (auto_approve when left out). Asynchronous: returns a request id.
  • delete_groupDelete groupDELETEAgents: ask firstDeletes a WhatsApp group with its real members. Asynchronous: returns a request id; the result arrives by webhook.
  • get_groupGet groupGETAgents: ask firstReturns one WhatsApp group: subject, description, join mode, suspended flag, creation time and participants (WhatsApp id, user id, username). Personal data.
  • get_group_invite_linkGet group invite linkGETAgents: ask firstReturns the current invite link of a WhatsApp group.
  • list_groupsList groupsGETAgents: ask firstLists the active WhatsApp groups of a business phone number (group id, subject, creation time), page by page with paging.after.
  • remove_group_participantsRemove group participantsPOSTAgents: ask firstRemoves up to 8 real participants from a WhatsApp group. Processed asynchronously: returns a request id; the result arrives by webhook, and get_group shows the members.
  • reset_group_invite_linkReset group invite linkPOSTAgents: ask firstReplaces the invite link of a WhatsApp group (the old link stops working) and returns the new one.
  • send_group_invite_linkSend group invite linkPOSTAgents: ask firstSends a real, billed WhatsApp template message carrying a group invite link to one user (not into the group). The template parameters must include one of type group_id.

Whatsapp flow, 7 operations

  • create_flowCreate flowPOSTAgents: ask firstCreates a WhatsApp Flow in a WABA, in DRAFT unless publish is true (which publishes it at once). Optional Flow JSON, a Flow to clone (cloneFlowId) and an endpoint URI.
  • delete_flowDelete flowDELETEAgents: ask firstDeletes a WhatsApp Flow; only a DRAFT Flow can be deleted (deprecate a published one with deprecate_flow).
  • deprecate_flowDeprecate flowPOSTAgents: ask firstMarks a published WhatsApp Flow as deprecated, the way to retire a Flow that can no longer be deleted.
  • get_flowGet flowGETAgents: ask firstReturns one WhatsApp Flow: name, status, categories, WABA, validation errors, JSON and data API versions, and endpoint URI.
  • get_flow_preview_urlGet flow preview urlGETAgents: ask firstReturns a public web preview URL of a WhatsApp Flow and its expiry (30 days). invalidate=true makes a new link.
  • list_flowsList flowsGETAgents: ask firstLists the WhatsApp Flows of a WABA: id, name, status, categories and validation errors.
  • publish_flowPublish flowPOSTAgents: ask firstSets a WhatsApp Flow to PUBLISHED. A published Flow cannot be deleted (deprecate_flow retires it, create_flow with cloneFlowId copies it); the vendor pages disagree on whether it can still be edited.

Unsubscriber, 5 operations

  • create_unsubscriberCreate unsubscriberPOSTAgents: ask firstRecords that a customer (E.164 phone number) opted out of WhatsApp messages; send_whatsapp_message with filterUnsubscribed=true then skips them.
  • delete_unsubscriberDelete unsubscriberDELETEAgents: ask firstDeletes a customer's opt-out for a channel (whatsapp), so messages can reach them again.
  • get_unsubscriberGet unsubscriberGETAgents: ask firstReturns a customer's opt-out record for one channel (whatsapp), or 404 when they have not opted out.
  • list_customer_unsubscribesList customer unsubscribesGETAgents: ask firstLists every opt-out recorded for one customer (E.164 phone number), one per channel.
  • list_unsubscribersList unsubscribersGETAgents: ask firstLists customers who opted out of WhatsApp messages from the business (phone number, channel, region, source, time), filtered by customer, channel or region. Personal data. Page with pageAfter.

Whatsapp message, 5 operations

  • get_whatsapp_messageGet whatsapp messageGETAgents: ask firstReturns one outbound WhatsApp message by its YCloud id: sender, recipient, type, content, status (accepted, sent, delivered, read, failed), error, pricing and timestamps. Personal data.
  • mark_message_as_readMark message as readPOSTAgents: ask firstMarks a received WhatsApp message (YCloud id or wamid) and every earlier one in that chat as read: the sender sees two blue check marks.
  • send_whatsapp_messageSend whatsapp messagePOSTAgents: ask firstQueues a real, billed WhatsApp message from a business number to a user: set type and the object of the same name. Returns the message with status accepted, not delivered; read get_whatsapp_message later.
  • send_whatsapp_message_directlySend whatsapp message directlyPOSTAgents: ask firstSends a real, billed WhatsApp message synchronously, for OTPs and time-sensitive messages: set type and the object of the same name. Unlike send_whatsapp_message it does not filter opt-outs.
  • show_typing_indicatorShow typing indicatorPOSTAgents: ask firstMarks a received WhatsApp message (YCloud id or wamid) and earlier ones as read and shows the sender a typing indicator until you reply or 25 seconds pass.

Whatsapp template, 5 operations

  • create_templateCreate templatePOSTAgents: ask firstCreates a WhatsApp message template (name, language, category AUTHENTICATION, MARKETING or UTILITY, components with at least a BODY). Only an APPROVED template can be sent: check its status with get_template.
  • delete_templateDelete templateDELETEAgents: ask firstDeletes one language of a WhatsApp template, by WABA, name and language code.
  • delete_templates_by_nameDelete templates by nameDELETEAgents: ask firstDeletes every language of a WhatsApp template name in a WABA (404 when none exists).
  • get_templateGet templateGETAgents: ask firstReturns one WhatsApp template by WABA, name and language: category, components, status (such as PENDING, APPROVED, REJECTED, PAUSED or ARCHIVED), quality and rejection reason.
  • list_templatesList templatesGETAgents: ask firstLists WhatsApp message templates (name, language, category, components, status, quality, rejection reason), page by page, filtered by WABA, name, language or comma-separated statuses.

Agent faq, 4 operations

  • create_agent_faqCreate agent faqPOSTAgents: ask firstAdds a question-and-answer entry to the agent's knowledge base, which the agent then uses in replies to customers.
  • delete_agent_faqDelete agent faqDELETEAgents: ask firstDeletes one FAQ entry from the agent's knowledge base.
  • get_agent_faqGet agent faqGETAgents: ask firstReturns one FAQ entry of the agent knowledge base: question, answer, creation time and metadata.
  • list_agent_faqsList agent faqsGETAgents: ask firstLists the question-and-answer entries in the agent's knowledge base.

Agent skill, 4 operations

  • create_agent_skillCreate agent skillPOSTAgents: ask firstAdds a behavioral skill (title, description, instruction text) that shapes how the agent answers customers.
  • delete_agent_skillDelete agent skillDELETEAgents: ask firstDeletes one behavioral skill from the agent.
  • get_agent_skillGet agent skillGETAgents: ask firstReturns one behavioral skill of the agent: title, description, instruction text, channel and creation time.
  • list_agent_skillsList agent skillsGETAgents: ask firstLists the agent's behavioral skills (title, description, instruction text). Pass agent_id to target one agent's settings.

Agent ui skill, 4 operations

  • create_agent_ui_skillCreate agent ui skillPOSTAgents: ask firstAdds a UI skill: a rich WhatsApp component the agent may send, with its instruction and status. flow_id only (and then required) when component_type is flow.
  • delete_agent_ui_skillDelete agent ui skillDELETEAgents: ask firstDeletes one UI skill from the agent.
  • get_agent_ui_skillGet agent ui skillGETAgents: ask firstReturns one UI skill: title, component type, status, instruction and Flow id.
  • list_agent_ui_skillsList agent ui skillsGETAgents: ask firstLists the rich WhatsApp components (carousels, CTA URLs, Flows, images...) the agent may send, page by page; keep paging while paging.next is present.

Agent website, 4 operations

  • add_agent_websiteAdd agent websitePOSTAgents: ask firstAdds a website URL for Meta to crawl into the agent knowledge base and returns the crawl entry.
  • delete_agent_websiteDelete agent websiteDELETEAgents: ask firstRemoves one website from the agent knowledge base.
  • get_agent_websiteGet agent websiteGETAgents: ask firstReturns one website knowledge entry: URL, crawl status, pages crawled, last crawl and creation times.
  • list_agent_websitesList agent websitesGETAgents: ask firstLists the website URLs Meta crawls into the agent knowledge base, with crawl status, pages crawled and last crawl time.

Business username, 4 operations

  • delete_business_usernameDelete business usernameDELETEAgents: ask firstRemoves the active WhatsApp business username of a phone number (a reserved request is kept); returns the new username status (not_set or reserved).
  • get_business_usernameGet business usernameGETAgents: ask firstReturns the WhatsApp business username state of a phone number: username, status (not_set, active, reserved, or legacy pending_review), requested username and update time.
  • list_business_username_suggestionsList business username suggestionsGETAgents: ask firstReturns the business usernames Meta suggests for a phone number, as a list of strings (empty when none).
  • request_business_usernameRequest business usernamePATCHAgents: ask firstRequests a public WhatsApp business username (@name) for a phone number; Meta may review it first (status reserved).

Contact, 4 operations

  • create_contactCreate contactPOSTAgents: ask firstCreates a YCloud contact from a unique E.164 phone number, with optional remark name, email, tags (up to 50), custom attributes, owner email and initial notes. Returns the contact (personal data).
  • delete_contactDelete contactDELETEAgents: ask firstDeletes a contact, identified by id, E.164 phone number (with +) or Meta username (without @), and returns the deleted contact.
  • get_contactGet contactGETAgents: ask firstReturns one contact by id, E.164 phone number (with +) or Meta username (without @): names, phone, email, tags, custom attributes, last seen time and source. Returns personal data.
  • list_contactsList contactsGETAgents: ask firstLists YCloud contacts (personal data: phone, email, names, tags, custom attributes), page by page, filtered by tags, country, phone number or email. For cursor paging pass pageAfter=0, then each cursor.after.

Webhook endpoint, 4 operations

  • create_webhook_endpointCreate webhook endpointPOSTAgents: ask firstSubscribes a public HTTPS URL (500 characters at most, no private address) to YCloud events; 20 endpoints per account. The signing secret is withheld from this answer.
  • delete_webhook_endpointDelete webhook endpointDELETEAgents: ask firstDeletes a webhook endpoint; YCloud stops sending events to it.
  • get_webhook_endpointGet webhook endpointGETAgents: ask firstReturns one webhook endpoint: url, subscribed events, event properties, description and status (active, disabled or pending). The signing secret is withheld.
  • list_webhook_endpointsList webhook endpointsGETAgents: ask firstLists the webhook endpoints of the account (url, subscribed events, event properties, description, status), page by page. Signing secrets are withheld.

Agent allowlist entry, 3 operations

  • add_agent_allowlist_entryAdd agent allowlist entryPOSTAgents: ask firstAdds one WhatsApp user, by E.164 consumer_phone_number or by consumer_bsuid (exactly one), to the agent allowlist (20 entries at most), so that user gets agent replies while ai_audience is ALLOWLISTED_ONLY.
  • delete_agent_allowlist_entryDelete agent allowlist entryDELETEAgents: ask firstRemoves one entry (id from list_agent_allowlist) from the agent allowlist; other entries stay.
  • list_agent_allowlistList agent allowlistGETAgents: ask firstLists the WhatsApp users (phone number or BSUID) allowed to get agent replies while ai_audience is ALLOWLISTED_ONLY. Personal data.

Agent business info, 3 operations

  • get_agent_business_infoGet agent business infoGETAgents: ask firstReturns the business information the agent uses to answer customers: payment method, return policy, purchase info, delivery and shipping, description and contact info (email, hours, address).
  • replace_agent_business_infoReplace agent business infoPUTAgents: ask firstCreates or fully replaces the agent's business information. Read get_agent_business_info first and send back every field to keep with your changes.
  • reset_agent_business_infoReset agent business infoDELETEAgents: ask firstResets the agent's business information (policies, shipping, description, contact info) to Meta's empty defaults and returns the result.

Agent file, 3 operations

  • delete_agent_fileDelete agent fileDELETEAgents: ask firstDeletes one uploaded knowledge file from the agent.
  • get_agent_fileGet agent fileGETAgents: ask firstReturns one knowledge file of the agent: id and file name.
  • list_agent_filesList agent filesGETAgents: ask firstLists the files uploaded as knowledge sources for the agent, with their ids and file names.

Contact note, 3 operations

  • create_contact_noteCreate contact notePOSTAgents: ask firstAdds a note to a contact (id, E.164 phone number or Meta username) and returns it. Not idempotent: repeating the call creates another note.
  • delete_contact_noteDelete contact noteDELETEAgents: ask firstDeletes one contact note by its id (from list_contact_notes) and returns the note as it was. A second delete of the same note answers 404.
  • list_contact_notesList contact notesGETAgents: ask firstLists the notes of one contact, newest first. Identify the contact by id, E.164 phone number (with +) or Meta username (without @). Returns personal data.

Group join request, 3 operations

  • approve_group_join_requestsApprove group join requestsPOSTAgents: ask firstApproves pending join requests (ids from list_group_join_requests): those real users join the group. Returns the approved and failed requests.
  • list_group_join_requestsList group join requestsGETAgents: ask firstLists the pending requests to join a WhatsApp group (request id, WhatsApp id, user id, username, time), page by page with paging.after. Personal data.
  • reject_group_join_requestsReject group join requestsPOSTAgents: ask firstRejects pending join requests (ids from list_group_join_requests). Returns the rejected and failed requests.

Messenger message, 3 operations

  • get_messenger_messageGet messenger messageGETAgents: ask firstReturns one outbound Messenger message by its YCloud id and the Facebook Page id (from): text, status, error code, timestamps and reactions, from YCloud records (Meta is not queried). Personal data.
  • get_messenger_message_by_meta_idGet messenger message by meta idGETAgents: ask firstReturns one outbound Messenger message sent through YCloud, looked up by the Facebook Page id (from) and its Meta message id: text, status, error code, timestamps and reactions. Personal data.
  • send_messenger_messageSend messenger messagePOSTAgents: ask firstSends a real one-to-one Messenger text reply from a connected Facebook Page (from) to a user PSID (to). Meta decides if a reply is allowed. Needs a tenant API key; developer app API keys are refused.

Whatsapp phone number, 3 operations

  • get_phone_numberGet phone numberGETAgents: ask firstReturns one WhatsApp business phone number: id, display number, quality rating, messaging limits, verified and requested names with their status, code verification, status, throughput and username.
  • list_phone_numbersList phone numbersGETAgents: ask firstLists the WhatsApp business phone numbers connected to YCloud: id (the phone number id), E.164 number, WABA, quality rating, messaging limit, verified name, status and business username.
  • register_phone_numberRegister phone numberPOSTAgents: ask firstRegisters a WhatsApp business phone number (by its phone number id, not E.164) with the WhatsApp Business Platform and returns the phone number record.

Agent budget, 2 operations

  • get_agent_budgetsGet agent budgetsGETAgents: ask firstReturns the agent usage budgets of the phone number's business (token or ai_turn limits per time window). An empty list means usage is unlimited.
  • replace_agent_budgetsReplace agent budgetsPUTAgents: ask firstReplaces the whole budget list: entries left out are removed and an empty list removes every limit. Read get_agent_budgets first and send back every entry to keep.

Agent settings, 2 operations

  • get_agent_settingsGet agent settingsGETAgents: ask firstReturns the agent settings as a list: rollout, handoff, follow-up and ai_audience per agent. Pass agent_id for one agent; without it Meta returns the channel's latest settings.
  • save_agent_settingsSave agent settingsPUTAgents: ask firstCreates or updates agent settings: rollout (turns replies on or off for real customers), handoff, follow-up, ai_audience (ALLOWLISTED_ONLY or EVERYONE) and never-say phrases. Leave out what you keep.

Blocked user, 2 operations

  • block_usersBlock usersPOSTAgents: ask firstBlocks real WhatsApp users (E.164 numbers in users, BSUIDs in userIds, 100 in all) from messaging a business phone number. Needs management permission on that number.
  • list_blocked_usersList blocked usersGETAgents: ask firstLists the users blocked on a business phone number, from Meta's blocklist (phone number, WhatsApp id, user id), page by page with pageAfter. Needs management permission. Personal data.

Business agent, 2 operations

  • delete_business_agentDelete business agentDELETEAgents: ask firstRemoves the Meta Business Agent from a WhatsApp phone number and deletes its configuration; on the account's last agent Meta also disconnects the integration. deleted_agent_id is null when there was none.
  • onboard_business_agentOnboard business agentPOSTAgents: ask firstStarts Meta Business Agent onboarding for a WhatsApp phone number (optionally with a Meta catalog id) and returns agent_id. It does not turn on customer replies; save_agent_settings does.

Event definition, 2 operations

  • create_event_definitionCreate event definitionPOSTAgents: ask firstDefines a custom event type (unique name, label, description) tied to contacts, with its typed properties (STRING, NUMBER, TIMESTAMP, URL), so send_custom_event can record occurrences.
  • get_event_definitionGet event definitionGETAgents: ask firstReturns one custom event definition by name: label, description, object type and its property definitions.

Event property, 2 operations

  • create_event_propertyCreate event propertyPOSTAgents: ask firstAdds a typed property (STRING, NUMBER, TIMESTAMP or URL) to a custom event definition.
  • delete_event_propertyDelete event propertyDELETEAgents: ask firstRemoves one property from a custom event definition.

Phone number settings, 2 operations

  • get_phone_number_settingsGet phone number settingsGETAgents: ask firstReturns the calling settings of a business phone number, or with type=capture its call recording and transcription capture settings.
  • save_phone_number_settingsSave phone number settingsPOSTAgents: ask firstSaves the calling settings, the call recording and transcription capture settings, or both, of a business phone number. Recording changes what is captured on real calls.

Sms, 2 operations

  • list_smsList smsGETAgents: ask firstLists SMS messages sent from the account (recipient, text, sender id, segments, price, status, error code), page by page; by default only the last day. Message texts can include codes sent by start_verification. Personal data.
  • send_smsSend smsPOSTAgents: ask firstSends a real, billed SMS to an E.164 phone number, with an optional sender id; a Chinese mainland message also needs an approved signature. Returns the SMS record, its price and status.

Voice code, 2 operations

  • list_voice_codesList voice codesGETAgents: ask firstLists voice-call verification codes sent from the account (recipient, language, price, status, error code), page by page; by default only the last day. The codes themselves are withheld. Personal data.
  • send_voice_codeSend voice codePOSTAgents: ask firstPlaces a real, billed phone call to an E.164 number that reads out a 4 to 6 digit verification code, in an optional language (default en). Returns the call record, its price and status.

Whatsapp business account, 2 operations

  • get_whatsapp_business_accountGet whatsapp business accountGETAgents: ask firstReturns one WhatsApp Business Account: name, currency, template namespace, review, business and verification status, country, ownership, payment and messaging details.
  • list_whatsapp_business_accountsList whatsapp business accountsGETAgents: ask firstLists the WhatsApp Business Accounts (WABAs) connected to YCloud: id, name, currency, review and business verification status, country. Use an id as wabaId elsewhere.

Whatsapp call, 2 operations

  • end_whatsapp_callEnd whatsapp callPOSTAgents: ask firstEnds an active WhatsApp call with a real user, by call id (wacid) and business phone number id.
  • reject_whatsapp_callReject whatsapp callPOSTAgents: ask firstRejects an incoming WhatsApp call from a real user (call id from the call connect webhook, business phone number id); the caller sees the call end.

Agent conversation turn, 1 operation

  • list_agent_conversation_turnsList agent conversation turnsGETAgents: ask firstLists the agent's conversation turns with one WhatsApp user (digits-only phone number), optionally between two epoch-millisecond times, with each LLM and tool step. Personal data.

Agent eligibility, 1 operation

  • check_agent_eligibilityCheck agent eligibilityGETAgents: ask firstReturns Meta's answer on whether the WhatsApp phone number (entityId) can use the Meta Business Agent: is_eligible.

Agent eval, 1 operation

  • get_agent_evalsGet agent evalsGETAgents: ask firstReturns per-conversation evaluation results (score, per-turn labels, reasons, transcript) for comma-separated eval ids from an evaluation summary.

Agent eval case, 1 operation

  • list_agent_eval_casesList agent eval casesGETAgents: ask firstLists the agent's evaluation scenarios: scenario, categories, turn limit and success criteria. Pass their ids to start_agent_eval_run.

Agent eval run, 1 operation

  • get_agent_eval_runGet agent eval runGETAgents: ask firstReturns the status, progress and, once done, the result (summary id, average scores, highlights) or error of an evaluation job from start_agent_eval_run.

Agent eval summary, 1 operation

  • get_agent_eval_summariesGet agent eval summariesGETAgents: ask firstReturns aggregated evaluation reports (scores, summary, highlights, top failure categories) for comma-separated summary ids from get_agent_eval_run.

Agent event, 1 operation

  • get_agent_eventGet agent eventGETAgents: ask firstReturns the processing status of an event from submit_agent_event: status, event type, error or skip reason, timestamps and conversation id.

Agent thread, 1 operation

  • control_agent_threadControl agent threadPOSTAgents: ask firstPasses, releases or takes control of a real customer's WhatsApp conversation (action pass, release or take) for the user given by to (E.164 or WhatsApp id) or recipient (BSUID), with optional metadata.

Balance, 1 operation

  • get_balanceGet balanceGETAgents: ask firstReturns the current YCloud account balance: amount and currency.

Business profile, 1 operation

  • get_phone_number_profileGet phone number profileGETAgents: ask firstReturns the public WhatsApp business profile of a phone number: about text, verified and requested names, address, description, email, picture URL, industry and websites.

Call media, 1 operation

  • download_call_mediaDownload call mediaGETAgents: ask firstDownloads the recording or transcription of a WhatsApp call made through the API, by the media asset id from a recording or transcription webhook, within 30 days. Personal data.

Commerce settings, 1 operation

  • get_commerce_settingsGet commerce settingsGETAgents: ask firstReturns whether the shopping cart and the catalog storefront are enabled in WhatsApp for a business phone number.

Contact attribute, 1 operation

  • list_contact_attributesList contact attributesGETAgents: ask firstLists every contact attribute available in the account with its key, type and allowed values, to know what create_contact and update_contact accept in customAttributes.

Contact book entry, 1 operation

  • delete_contact_book_entryDelete contact book entryDELETEAgents: ask firstDeletes the Meta contact book entry linking a business phone number to a customer's standard BSUID (parent .ENT. BSUIDs are refused).

Creative optimization, 1 operation

  • get_waba_creative_optimizationsGet waba creative optimizationsGETAgents: ask firstReturns a WABA's enrollment in Meta's automatic creative optimization features (image touch-ups, text overlays, CTA text...), read from Meta.

Custom event, 1 operation

  • send_custom_eventSend custom eventPOSTAgents: ask firstRecords an occurrence of a defined custom event for a contact (by contact id, phone number or Meta username), with its properties. It can start YCloud automations set on that event.

Email, 1 operation

  • send_emailSend emailPOSTAgents: ask firstSends a real, billed email from an address on a domain registered and activated in YCloud to up to 100 recipients, with optional cc, bcc, reply-to and #var# variables per recipient. Returns the email record and its status.

Template analytics, 1 operation

  • get_template_analyticsGet template analyticsPOSTAgents: ask firstReturns daily metrics for one template (sent, delivered, read, failed, clicks, replies) between two dates (1 to 90 days, WABA timezone), plus Meta Template Insights when available.

Verification, 1 operation

  • check_verificationCheck verificationPOSTAgents: ask firstChecks a code a user typed against a verification, by verificationId or by the phone number or email it was sent to. valid true approves it (status approved); an approved verification cannot be checked again.

Showing the first 120 of 145 endpoints. The rest are in the product, searchable from the workflow builder and from chat.

Use YCloud from Claude Code, Cursor or Codex

Connect YCloud in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its YCloud operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect YCloud

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect YCloud once

    Add your YCloud connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

YCloud integration FAQ

What can you do with the YCloud integration?

LiveContext exposes 145 operations on YCloud, covering whatsapp group, whatsapp flow, unsubscriber and whatsapp message.

Popular integrations

Browse the whole catalog