Execute store updates from internal chat discussions
When a team member posts a status update in a specific channel in Campsite, execute a custom API request in Whop to update inventory or store settings.
See all Campsite + Whop integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Campsite Explore Campsite →
TriggersFires when a new message is posted to a channel in Campsite.
Fires when your team or a keyword is mentioned in Campsite.
Fires when a new channel is created in Campsite.
Fires when a new file is shared in Campsite.
Posts a message to a channel in Campsite.
Sends a direct message to a person in Campsite.
Creates a new channel in Campsite.
Adds a user to a channel in Campsite.
Whop Explore Whop →
TriggersFires when a customer places a new order in Whop.
Fires when an order in Whop is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in Whop.
Fires when a customer abandons their cart before completing checkout in Whop.
Creates or updates a product or listing in Whop.
Updates an order's status or fulfillment details in Whop.
Sends a custom API request to Whop for actions not covered by a dedicated action.
More Campsite + Whop workflows
See all Campsite + Whop integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Execute store updates from internal chat discussions” between Campsite and Whop?
Yes — describe it in the box above and Knit's Integrations Agent researches Campsite and Whop's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why should I send store updates from Whop into Campsite?
It brings real-time commerce events into your team's existing workspace, helping marketing and sales reps respond instantly to high-intent customer behavior or partnership updates.
Can team conversations in Campsite update data in Whop?
Yes, posting specific updates or messages in Campsite can initiate a custom API request to update orders, products, or customer data in Whop.