Zylvie MCP integration for AI agents.
Connect AI agents to Zylvie through 12 structured actions, including get current user, create coupon, delete coupon, and redeem license key. Review authentic…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Zylvie integration exposes
The Zylvie Agent App exposes 12 provider-backed actions for marketing and finance work. Its current contract lets an authorized agent get the zylvie user and brand authenticated by the current api key, create a coupon in zylvie, and delete a zylvie coupon, or archive it when transaction history requires it. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Zylvie account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Zylvie capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the Zylvie user and brand authenticated by the current API key.
create_couponWRITECreate a coupon in Zylvie.
INPUTS: code / type / amount / isStorewide / productIds
delete_couponHIGH IMPACTDelete a Zylvie coupon, or archive it when transaction history requires it.
INPUTS: id
redeem_license_keyREVIEWMark a Zylvie license key as redeemed.
INPUTS: licenseKey
create_productWRITECreate a product in Zylvie.
INPUTS: title / url / currency / price / pricingModel
delete_productHIGH IMPACTDelete a Zylvie product, or archive it when transaction history requires it.
INPUTS: id
list_couponsREADList active or archived coupons for the authenticated Zylvie brand.
INPUTS: archived
refund_license_keyHIGH IMPACTMark a Zylvie license key as refunded.
INPUTS: licenseKey
update_couponWRITEUpdate selected fields on an existing Zylvie coupon.
INPUTS: id / code / type / amount / isStorewide
update_productWRITEUpdate selected fields on an existing Zylvie product.
INPUTS: id / title / url / currency / price
verify_license_keyREVIEWVerify that a Zylvie license key is valid for a product.
INPUTS: productId / licenseKey
verify_subscriptionsREVIEWList Zylvie subscriptions associated with a subscriber email address.
INPUTS: email
INPUT CONTRACTS
Know what the action needs before it runs.
create_coupon
codeREQUIRED- The unique case-insensitive coupon code.
typeREQUIRED- The discount calculation type.
amountREQUIRED- The discount amount.
isStorewideOPTIONAL- Whether the coupon applies to every product.
productIdsOPTIONAL- The product IDs to which a non-storewide coupon applies.
delete_coupon
idREQUIRED- The Zylvie object identifier.
redeem_license_key
licenseKeyREQUIRED- The license key issued by Zylvie.
create_product
titleREQUIRED- The product title.
urlREQUIRED- The unique vanity URL slug.
currencyREQUIRED- The lowercase ISO 4217 currency code.
priceREQUIRED- The base product price.
pricingModelREQUIRED- The product billing model.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the Zylvie user and brand authenticated by the current API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Coupon
Create a coupon in Zylvie. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_couponVerify with List Coupons
List active or archived coupons for the authenticated Zylvie brand. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_couponsSAFETY BOUNDARY
Operate Zylvie with explicit limits
- Authorize Zylvie with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_coupon`, `delete_product`, and `refund_license_key` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Zylvie rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Zylvie task completed successfully.
CONNECTION MODEL
API key
Zylvie API key sent as a Bearer token. Copy it from https://developers.zylvie.com/settings/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Zylvie.