Run any Skill in Manus with one click

ycloud

Stars3

Forks0

UpdatedJuly 7, 2026 at 18:27

YCloud — a multi-channel communications provider (CPaaS: WhatsApp, SMS, Voice, Email), not a Meta-only BSP. This skill covers its WhatsApp Business operations: console navigation, account creation/onboarding, Embedded Signup, campaigns/inbox/journeys, auto-unsubscribe chatbot, the public-API-vs-dashboard-backend distinction, BSP migration, and read-only CDP automation. Use when operating YCloud for WhatsApp dispatch: embedded signup, campaign sends, campaign analytics, inbox, auto-unsubscribe chatbot, opt-out attribution, dashboard automation. Triggers on: 'ycloud', 'CPaaS', 'BSP', 'bulk campaign', 'whatsapp dashboard', 'embedded signup', 'auto-unsubscribe', 'opt-out chatbot', 'campaign analytics', 'dispatch automation', 'ycloud free plan', 'zero markup', 'ycloud account creation', 'ycloud onboarding', 'ycloud signup code'.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

andredezzy

andredezzy/maccing

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

File Explorer

3 files

SKILL.md

readonly

name

ycloud

description

Related: whatsapp (Cloud API + dispatch + BSP pricing/billing), ycloud-api (the v2 REST API reference), meta (BM/isolation — the CDP automation MUST run inside the disposable BM's AdsPower profile).

Overview

YCloud is a multi-channel communications provider (CPaaS — WhatsApp, SMS, Voice, Email). This skill focuses on its WhatsApp Business Solution Provider (BSP) role, which wraps Meta's WhatsApp Business API. The Free plan has:

$0/month subscription, unlimited API access
0% per-message markup — wallet is debited at Meta's base rate (~$0.0625/msg for Brazil marketing)
Shared inbox, 1 user, 2 channels included
Embedded Signup: no Meta developer account needed; only Facebook login + BM Admin access

This makes YCloud the best-value Brazil dispatch option at any volume: you pay only Meta's rate. The Growth ($39/mo), Pro ($89/mo), and Enterprise ($399/mo) plans add users, channels, and AI credits at the same 0% markup.

For BSP comparison, plan details, and pricing model see whatsapp → references/pricing-and-billing.md.

Risk: free-tier accounts in financial niches have been false-positive-suspended. Resolution via support ticket typically takes <24h. One BSP account per disposable BM is required (recommended practice) to prevent a single suspension from taking down all active BMs.

Account onboarding ≠ Embedded Signup. Creating the YCloud account (a 5-step wizard) is separate from connecting a WABA (Embedded Signup). The account-signup verification code is delivered via a WhatsApp message (not email/SMS) — a non-obvious blocker on disposable-BM setups, since it can reuse neither another BM's WhatsApp nor the fresh WABA chip. Full per-BM onboarding flow + the burner-WhatsApp workaround + account email/domain + profiling-field guidance + the $0.50 signup credit: references/account-and-waba-setup.md → Account Creation / Onboarding (per BM).

Console Map

Area	Path	What it does
Campaigns (bulk send)	Campaigns → WhatsApp Campaigns	Upload `.xlsx` list, pick template, send to many
Campaign analytics	Campaign row → Analytics/Logs tab	Real-time per-recipient funnel; campaign ID is in URL
Inbox	Inbox	Per-conversation inbound + manual agent replies
Auto-unsubscribe chatbot	AI Agent → Create Agent (Rule-based)	Keyword-triggered Unsubscribe node; must assign to number
Templates	WhatsApp → Templates	Create / list / check approval status
Phone numbers	WhatsApp → Phone Numbers	Quality rating, messaging tier, profile
Wallet	Billing → Wallet	Balance top-up, transaction view
Webhooks	Developer → Webhooks	Subscribe to `whatsapp.message.updated`
API key	Developer → API Keys	The `X-API-Key` for the public REST API

Public API vs Dashboard Backend

YCloud exposes two separate APIs:

Public REST API (api.ycloud.com/v2, X-API-Key header):

Per-message delivery status, cost, template approval, phone quality, wallet balance
Real-time for sendDirectly API sends; campaign (bulk UI) messages lag by hours
No campaign/activity concept — no bulkMessages endpoint (returns 404)

Dashboard backend (www.ycloud.com/api/..., SESSION cookie):

Per-campaign unsubscribeNums, per-button click counts, per-recipient search within a campaign
Undocumented, SESSION-cookie only (rejects the public API key)
MUST be reached from inside the disposable BM's AdsPower profile (see references/api-automation.md)

Campaign-send LAG is critical: after a campaign completes and the wallet is charged, the messages may not appear in /v2/whatsapp/messages for hours (sometimes next-day). Use the campaign's Analytics/Logs tab or whatsapp.message.updated webhooks for real-time monitoring.

For the read-only automation discipline (CDP connect, the MCP read recipe, undetectability), see references/api-automation.md.

Routing Table

Intent	Reference	Use for
Account signup wizard, WhatsApp-code gotcha + workaround, account email/domain, profiling fields, $0.50 credit	references/account-and-waba-setup.md	Creating a new YCloud account per BM
Embedded Signup steps, WABA connection, opt-out chatbot setup	references/account-and-waba-setup.md	Connecting a WABA + building keyword opt-out flows
Campaign send file format, `.xlsx` spec, Test-send button	references/account-and-waba-setup.md	Preparing and uploading campaign lists
BSP comparison table, pricing model, YCloud plans	whatsapp → references/pricing-and-billing.md	Choosing or justifying BSP selection
evaluate.py, Dashboard Backend API, SESSION cookie auth	references/api-automation.md	Pulling per-campaign analytics programmatically
Reconciliation: unanswered inbox replies, per-campaign stats	references/api-automation.md	Every YCloud reconcile: pull unanswered inbound + raise as #1 action
Template scoring, what's automatable capability table	references/api-automation.md	Understanding automation boundaries
AdsPower MCP read recipe, automation loop code	references/api-automation.md	Automating dashboard backend reads
Read/commit split, rung assignment for YCloud tasks	references/api-automation.md	Architecture of read-only automation
Isolation rule (AdsPower profile, proxy, BSP-per-BM)	references/api-automation.md	Safe automation without ban risk

More from this repository

same repository

notion

andredezzy/maccing

Use BEFORE the first Notion read or write on ANY task touching Notion — the Notion API or its MCP — however trivial: a one-field rename, a page icon/cover, adding one row, a single select color, even just reading a page's title. Covers creating, editing, querying, or moving databases, data sources, pages, views (table/board/gallery/calendar/timeline/list/chart/dashboard/map/form), formulas, rollups, relations, blocks, icons, covers; and any Notion API/MCP error (validation_error, pagination, permission, 400/409). MANDATORY, never optional — "small", "quick", "obvious", or "well-understood" is the exact trap: every Notion edit still owes this skill's mandatory first steps (the ancestral-AGENTS.md sweep + house-style match) that a direct quick edit silently skips and corrupts. If the work touches Notion at all, load this FIRST.

2026-07-173

naming

andredezzy/maccing

Use when naming anything — files, functions, types, variables, enum members — or choosing between a boolean, string union, and enum for a set of states. Triggers: a status/state field, vague or abbreviated names, single-letter values, Base-prefixed classes, Contract-suffixed interfaces, casing questions, PascalCase filenames, a name that covers only part of what the function does, a mechanism or pattern you invented a name for (a *Limiter/*Pool/*Gate) when the trade may already name it.

2026-07-113

researching-before-coding

andredezzy/maccing

Use when about to write code against any external library, API, framework, or tool; when hitting an error, incompatibility, or unfamiliar technology; when introducing or naming a mechanism that solves a recognized problem (a limiter, pool, queue, retry/isolation primitive) even when its code is pure internal logic; before proposing a fix or presenting a design. Especially when confident from memory, under time pressure, when the API "is well known", or when a mechanism "is just internal logic".

2026-07-113

organizing-code

andredezzy/maccing

Use when creating, splitting, or moving files; defining error classes or writing catch blocks; adding helpers, wrappers, or utils; structuring test files; or deciding where types, env vars, or server/client context live. Triggers: a file doing several things, circular imports, barrel files, a function that only forwards its arguments, a buildX(config) helper re-reading inputs a component already receives, an empty catch, a dense wall of code, inline multi-property object types, section-divider comments.

2026-07-113

composing-ui

andredezzy/maccing

Use when creating any UI component, page, route, or layout, adding a prop to an existing one, wiring data fetching for a screen (prefetch, hydration, suspense, skeletons), or touching a component that has grown large — React or any component framework — plus forms, styling, and labels. Triggers: a prop toggling a section, a god component, dot-notation sub-components (Card.Header), raw inputs with hand-rolled validation, title-case labels, "just one more prop", a page marked "use client", a dataset passed as a prop to a client component, a route-level loading file, a page re-checking auth, a client-side re-parse of search params.

2026-07-103

modeling-domains

andredezzy/maccing

Use when defining domain types, database or validation schemas, config shapes, wire payloads, or translation/message trees; when adding a domain type, union member, registry, or dispatcher; when data is flat, joined by ID references, duplicated across fields, or its nesting does not match the real-world thing it describes. Distinct from glossary-style domain-modeling: this skill dictates STRUCTURE — isomorphism, containment, registries.

2026-07-073

name

ycloud

description

Related: whatsapp (Cloud API + dispatch + BSP pricing/billing), ycloud-api (the v2 REST API reference), meta (BM/isolation — the CDP automation MUST run inside the disposable BM's AdsPower profile).

Overview

$0/month subscription, unlimited API access
0% per-message markup — wallet is debited at Meta's base rate (~$0.0625/msg for Brazil marketing)
Shared inbox, 1 user, 2 channels included
Embedded Signup: no Meta developer account needed; only Facebook login + BM Admin access

For BSP comparison, plan details, and pricing model see whatsapp → references/pricing-and-billing.md.

Console Map

Area	Path	What it does
Campaigns (bulk send)	Campaigns → WhatsApp Campaigns	Upload `.xlsx` list, pick template, send to many
Campaign analytics	Campaign row → Analytics/Logs tab	Real-time per-recipient funnel; campaign ID is in URL
Inbox	Inbox	Per-conversation inbound + manual agent replies
Auto-unsubscribe chatbot	AI Agent → Create Agent (Rule-based)	Keyword-triggered Unsubscribe node; must assign to number
Templates	WhatsApp → Templates	Create / list / check approval status
Phone numbers	WhatsApp → Phone Numbers	Quality rating, messaging tier, profile
Wallet	Billing → Wallet	Balance top-up, transaction view
Webhooks	Developer → Webhooks	Subscribe to `whatsapp.message.updated`
API key	Developer → API Keys	The `X-API-Key` for the public REST API

Public API vs Dashboard Backend

YCloud exposes two separate APIs:

Public REST API (api.ycloud.com/v2, X-API-Key header):

Per-message delivery status, cost, template approval, phone quality, wallet balance
Real-time for sendDirectly API sends; campaign (bulk UI) messages lag by hours
No campaign/activity concept — no bulkMessages endpoint (returns 404)

Dashboard backend (www.ycloud.com/api/..., SESSION cookie):

Per-campaign unsubscribeNums, per-button click counts, per-recipient search within a campaign
Undocumented, SESSION-cookie only (rejects the public API key)
MUST be reached from inside the disposable BM's AdsPower profile (see references/api-automation.md)

For the read-only automation discipline (CDP connect, the MCP read recipe, undetectability), see references/api-automation.md.

Routing Table

Intent	Reference	Use for
Account signup wizard, WhatsApp-code gotcha + workaround, account email/domain, profiling fields, $0.50 credit	references/account-and-waba-setup.md	Creating a new YCloud account per BM
Embedded Signup steps, WABA connection, opt-out chatbot setup	references/account-and-waba-setup.md	Connecting a WABA + building keyword opt-out flows
Campaign send file format, `.xlsx` spec, Test-send button	references/account-and-waba-setup.md	Preparing and uploading campaign lists
BSP comparison table, pricing model, YCloud plans	whatsapp → references/pricing-and-billing.md	Choosing or justifying BSP selection
evaluate.py, Dashboard Backend API, SESSION cookie auth	references/api-automation.md	Pulling per-campaign analytics programmatically
Reconciliation: unanswered inbox replies, per-campaign stats	references/api-automation.md	Every YCloud reconcile: pull unanswered inbound + raise as #1 action
Template scoring, what's automatable capability table	references/api-automation.md	Understanding automation boundaries
AdsPower MCP read recipe, automation loop code	references/api-automation.md	Automating dashboard backend reads
Read/commit split, rung assignment for YCloud tasks	references/api-automation.md	Architecture of read-only automation
Isolation rule (AdsPower profile, proxy, BSP-per-BM)	references/api-automation.md	Safe automation without ban risk