Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

sales-funnelkit

Sterne58

Forks7

Aktualisiert28. Juni 2026 um 10:44

FunnelKit (funnelkit.com, formerly WooFunnels/Autonami) platform help — WordPress/WooCommerce sales-funnel builder + built-in CRM/marketing-automation suite: checkout, order bumps, one-click upsells/downsells, A/B testing, sliding cart, plus FunnelKit Automations (email/SMS, contact segments, broadcasts, cart-abandonment recovery). Developer surface: FunnelKit Automations REST API (`/wp-json/funnelkit-automations/`, api_key query param) with Tags/Lists/Fields/Contacts CRUD + incoming/outgoing webhooks, and WooCommerce order hooks/REST for funnel revenue. Use when adding or segmenting contacts via the API, wiring incoming/outgoing webhooks, building one-click upsells or order bumps, recovering abandoned carts, reading funnel revenue via WooCommerce, or choosing Funnel Builder vs Automations vs the bundles. Do NOT use for funnel/CRO strategy across tools (use /sales-funnel), checkout-conversion strategy (use /sales-checkout), or generic iPaaS wiring (use /sales-integration).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

sales-skills

sales-skills/sales

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Datei-Explorer

4 Dateien

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

sales-do

sales-skills/sales

Routes any sales, marketing, ad, or GTM objective to the right specialized skill and outputs the install command for that skill plus a ready-to-paste prompt packed with the user's context. Asks clarifying questions when the objective is ambiguous, then hands back a copy-paste-runnable next step. Covers prospecting, outbound cadences, deals, proposals, forecasting, deliverability, enrichment, intent, content, coaching, CRO, SEO, launch directories, newsletters, email/SMS/push marketing, chatbots, influencer marketing, social media, employee advocacy, media relations, reviews, data hygiene, B2B advertising, retargeting, affiliate, loyalty, digital products, memberships, webinars, checkout, and platform-specific help. Use when the user has a sales or marketing question and isn't sure which skill to use, or wants a multi-skill sequence with a batch install command. Do NOT use to solve problems directly — this skill only routes.

2026-06-2858

sales-phantombuster

sales-skills/sales

PhantomBuster (phantombuster.com) platform help — code-free web/LinkedIn automation + scraping + lead-gen: 'Phantoms' (LinkedIn search export, scrapers, auto-connect, email finder), Flows that chain them, AI Agents + a cloud LinkedIn Leads database. Developer surface: a REST API (base phantombuster.com/api/v2, X-Phantombuster-Key-1 header) to launch agents (POST /agent/{id}/launch → container id) and fetch run results (/containers/fetch-result-object), plus the Leads storage and per-agent webhooks (secret param, 11s timeout) on run completion. Billed by execution time + slots; API on all paid plans. Use when launching a Phantom or fetching its scraped output via the API, wiring a run-finished webhook, handling the async agent→container model, managing slots/execution-time, or LinkedIn cookie/safety issues. Do NOT use for prospect-list / lead-sourcing strategy across tools (use /sales-prospect-list), enrichment strategy across vendors (use /sales-enrich), or outbound cadence strategy (use /sales-cadence).

2026-06-2858

sales-prospect-list

sales-skills/sales

Builds targeted B2B prospect lists for outbound campaigns from database providers (Apollo, ZoomInfo, Clay, Cognism). Use when you don't know who to target, your outbound list is too broad and response rates are low, you can't find the right decision-makers at target accounts, your ICP is vague, or your prospect list is full of bad-fit contacts. Do NOT use for enriching existing contacts with emails/phones (use /sales-enrich), interpreting buying signals (use /sales-intent), general Apollo platform help (use /sales-apollo), or hyperlocal / door-to-door / territory / route-based outbound to local SMBs that aren't on databases — restaurants, gas stations, salons, contractors, HVAC — (use /sales-field-sales).

2026-06-2858

sales-intent

sales-skills/sales

Interprets buying signals and prioritize accounts for outreach. Use when drowning in intent data and not sure what matters, can't tell which accounts to prioritize, buying signals aren't translating to pipeline, job change alerts are noisy, intent topics feel too broad, lead scores don't match actual deal quality, or not sure how to act on signals in outreach. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), ZoomInfo-specific intent config (use /sales-zoominfo), or general Apollo platform help (use /sales-apollo).

2026-06-2858

sales-syncgtm

sales-skills/sales

SyncGTM (syncgtm.com) platform help — AI-native GTM data engine that unifies buying signals (job changes, funding, hiring, LinkedIn posts, web-traffic, custom AI signals), waterfall enrichment (verified emails/mobiles, 40+ providers), AI lead scoring (0–100 vs ICP), AI research agents, and a no-code Workflow Builder. Developer surface: an MCP server (api.syncgtm.com/mcp, OAuth browser sign-in, free-plan — works with Claude Code/Cursor to enrich, find emails/phones, read signals), a REST API (api.syncgtm.com, API key), webhooks, and 40+ integrations (HubSpot/Salesforce/Slack/Attio). Use when connecting the MCP server to an AI agent, enriching contacts via the API, acting on buyer signals, scoring leads vs an ICP, building a signal→enrich→outreach workflow, or choosing SyncGTM vs Clay/Trigify. Do NOT use for intent-data strategy across tools (use /sales-intent), prospect-list building (use /sales-prospect-list), or enrichment strategy across vendors (use /sales-enrich).

2026-06-2858

sales-cadence

sales-skills/sales

Designs multi-channel outbound cadences with timing, A/B testing, and content. Use when outbound sequences getting low reply rates, unsure how many touchpoints or what spacing to use, cadence emails sound generic, prospects ignoring calls, A/B tests not moving the needle, sequence performance plateauing, or not sure which channels to include in outreach. Do NOT use for marketing cold email (use /cold-email), automated email flows (use /email-sequence), or general Salesloft platform help (use /sales-salesloft).

2026-06-2858

name	sales-funnelkit
description	FunnelKit (funnelkit.com, formerly WooFunnels/Autonami) platform help — WordPress/WooCommerce sales-funnel builder + built-in CRM/marketing-automation suite: checkout, order bumps, one-click upsells/downsells, A/B testing, sliding cart, plus FunnelKit Automations (email/SMS, contact segments, broadcasts, cart-abandonment recovery). Developer surface: FunnelKit Automations REST API (`/wp-json/funnelkit-automations/`, api_key query param) with Tags/Lists/Fields/Contacts CRUD + incoming/outgoing webhooks, and WooCommerce order hooks/REST for funnel revenue. Use when adding or segmenting contacts via the API, wiring incoming/outgoing webhooks, building one-click upsells or order bumps, recovering abandoned carts, reading funnel revenue via WooCommerce, or choosing Funnel Builder vs Automations vs the bundles. Do NOT use for funnel/CRO strategy across tools (use /sales-funnel), checkout-conversion strategy (use /sales-checkout), or generic iPaaS wiring (use /sales-integration).
argument-hint	[describe what you need help with in FunnelKit]
license	MIT
version	1.0.0
tags	["sales","funnel","wordpress","platform"]
github	https://github.com/funnelkit

FunnelKit Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

What are you trying to do?
- A) Add/update/segment contacts (tags, lists, fields, status) via the Automations REST API
- B) Wire incoming/outgoing webhooks (receive external events → automation; or send data out)
- C) Build the funnel — checkout, order bumps, one-click upsells/downsells, A/B testing, sliding cart
- D) Recover abandoned carts / run email-SMS automations (FunnelKit Automations)
- E) Read funnel revenue/orders programmatically (via WooCommerce)
- F) Decide Funnel Builder vs Automations vs a bundle, or Free vs Pro
Which side? Contacts/email/SMS/automation → FunnelKit Automations (REST API + webhooks). Checkout/upsells → Funnel Builder (WooCommerce orders).

Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.

Step 2 — Route or answer directly

If the question is about...	Route to...
Funnel / CRO strategy across tools (which builder, funnel design)	`/sales-funnel {question}`
Checkout/cart conversion strategy across platforms	`/sales-checkout {question}`
Connecting FunnelKit to a CRM/ESP generically (iPaaS)	`/sales-integration {question}`
Email/SMS sequence strategy beyond FunnelKit Automations	`/sales-email-marketing {question}`

When routing, give the exact command, e.g. "This is a strategy question — run: /sales-funnel design a post-purchase upsell flow".

Step 3 — FunnelKit platform reference

Read references/platform-guide.md for the full reference — the two-product model (Funnel Builder vs Automations), what's REST-API vs WooCommerce vs UI-only, best-effort pricing/bundles, the contact data model, and quick-start recipes (add+segment a contact; receive an incoming webhook; read orders via WooCommerce).

Read references/funnelkit-api-reference.md for the integration surface — FunnelKit Automations REST API (base /wp-json/funnelkit-automations/, ?api_key= query-param auth from Settings → REST API; Tags/Lists/Fields/Contacts CRUD, offset pagination, {code,data,limit,offset} responses), incoming + outgoing webhooks, and WooCommerce order hooks/REST for funnel revenue.

Answer using only the relevant section. Don't dump the full reference.

Step 4 — Actionable guidance

Focus on the user's specific situation:

Two products, two surfaces. Automations (CRM/email/SMS) has the REST API + webhooks; the Funnel Builder (checkout/upsells) rides on WooCommerce — read its revenue via the WooCommerce REST API, not a FunnelKit endpoint.
The API key is a query param. Auth is ?api_key=... (from Automations Settings → REST API) — not a header. Keep URLs out of logs/referrers and call server-side.
Contacts are tag/list-driven. Create with POST /contact/add, then tag-assign/list-assign to segment — automations trigger off tags/lists/status. Status is subscribed|bounced|unsubscribed|verified.
Webhooks go both ways. Use the incoming Webhook URL to feed external events into an automation; use the HTTP Request action for outgoing webhooks. Treat the incoming URL as a secret and capture a live payload (schema isn't fully published).
AOV is the funnel job. Rule-based order bumps + one-click upsells/downsells (post-purchase, charged to the original WooCommerce order) + sliding cart are the revenue levers; A/B test the offers.
It's WordPress-only. No hosted SaaS/MCP; you need a self-hosted WordPress + WooCommerce site. Free version exists; advanced funnel + Automations features are Pro/bundle-gated (best-effort pricing — verify).

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research (2026-06) — pricing/feature specifics verified against the marketing site, developer docs, and comparison articles; confirm in-account.

API is the Automations side only. /wp-json/funnelkit-automations/ manages contacts/tags/lists/fields — there's no funnel-builder read API; funnel orders/revenue come from WooCommerce.
?api_key= is a query param. Not a header — it can leak via logs/referrers; keep calls server-side and rotate the key if exposed.
WordPress + WooCommerce required. No hosted API/MCP; everything runs on your self-hosted site, and commerce needs WooCommerce.
Webhook payloads aren't fully documented. The overview lists incoming/outgoing + conditions but not full schemas/signatures — capture a live delivery and treat the incoming URL as secret.
Two products + bundles. Funnel Builder and Automations are separate (each Free + Pro); bundles (Plus/Professional/Elite) gate which you get. Price the bundle, not just one plugin (best-effort ~$99.50–$399/yr).
One-click upsells need gateway support. Post-purchase one-click charges require a compatible WooCommerce gateway (Stripe/PayPal/etc.).
Formerly WooFunnels/Autonami. Old docs/threads use those names — "Autonami" = FunnelKit Automations.

Related skills

/sales-funnel — Sales-funnel / CRO strategy across tools (FunnelKit is one of the WordPress funnel builders covered) — funnel design, tool selection vs CartFlows/WPFunnels
/sales-checkout — Checkout/cart conversion (order bumps, one-click upsells, AOV) across platforms
/sales-email-marketing — Email/SMS sequence strategy beyond FunnelKit Automations
/sales-integration — Connecting FunnelKit to a CRM/ESP via REST API/webhooks/Zapier/WooCommerce
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: Add and segment a contact via the Automations API (developer/automation)

User says: "When someone buys in my app, how do I add them to FunnelKit Automations and tag them via the API?" Skill does: Walks Recipe 1 — POST /wp-json/funnelkit-automations/contact/add?api_key=... with the email/name, then POST /contact/tag-assign/{contact_id} with {"tags":[id]} (and list-assign for a list). Notes the api_key query-param auth (Settings → REST API), the {code,data,limit,offset} response, status values, and that tags/lists are what trigger automations. Flags keeping the key server-side. Result: Buyers land in Automations correctly tagged, ready to trigger a flow.

Example 2: Receive an external event via incoming webhook

User says: "My payment processor should add a contact to a FunnelKit automation when a subscription renews." Skill does: Explains the incoming Webhook URL (set up a webhook-triggered automation in FunnelKit Automations), plug that URL into the processor, and use Conditions to branch on the payload; the automation can then add/tag the contact and send email/SMS. Notes the payload schema isn't fully published (capture a live delivery) and to treat the URL as secret. Offers Zapier as a no-code alternative. Result: Renewals drive a FunnelKit automation in real time.

Example 3: Funnel Builder vs Automations vs a bundle — what do I buy?

User says: "Do I need FunnelKit Funnel Builder, Automations, or both?" Skill does: Distinguishes Funnel Builder (checkout, order bumps, one-click upsells, A/B testing — the AOV/checkout layer) from Automations (CRM, email/SMS, cart-abandonment, segments — the marketing layer), notes each has Free + Pro and that bundles (Plus/Professional/Elite) combine them. Recommends both for a full WooCommerce funnel + recovery stack; frames pricing as best-effort (~$99.50–$399/yr) and routes tool-selection vs CartFlows/WPFunnels to /sales-funnel. Result: User buys the right combination for their stack.

Troubleshooting

My API calls return 401/403

Symptom: Requests to /wp-json/funnelkit-automations/... are rejected. Cause: Missing/invalid api_key query param, or the key wasn't generated/enabled in Automations Settings → REST API. Solution: Generate the key in Automations → Settings → REST API, append ?api_key={key} to every request (it's a query param, not a header), and use HTTPS. Confirm the base path is /wp-json/funnelkit-automations/ on your site. 403 can also mean a security plugin/host is blocking the REST route.

I can't find an API to read my funnel's orders/upsells

Symptom: Looking for a FunnelKit endpoint for funnel revenue. Cause: The REST API is the Automations (contacts) side; the Funnel Builder runs on WooCommerce orders and has no separate read API. Solution: Read order bumps + one-click upsells as WooCommerce orders via the WooCommerce REST API (/wp-json/wc/v3/orders) or WooCommerce order webhooks. Use FunnelKit Automations' API/webhooks for the contact/marketing side.

My one-click upsell isn't charging

Symptom: Post-purchase upsell doesn't complete the charge. Cause: One-click upsells require a WooCommerce payment gateway that supports post-purchase charges (e.g. Stripe/PayPal as integrated by FunnelKit); not all gateways qualify. Solution: Use a supported gateway, confirm FunnelKit Funnel Builder Pro is active, rebuild the upsell step, and test a full checkout. For AOV strategy across tools, use /sales-checkout.