Tremendous MCP integration for AI agents.
Connect AI agents to Tremendous through 13 structured actions, including get campaign, create order, and generate reward link. Review authentication, inputs…
- ACTION CONTRACTS
- 13
- 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 Tremendous integration exposes
The Tremendous Agent App exposes 13 provider-backed actions for finance and marketing work. Its current contract lets an authorized agent retrieve one tremendous campaign by id, create a tremendous reward order with an optional external id for idempotent retries, and generate a redemption link for an existing tremendous reward. 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 Tremendous account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Tremendous capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaignREADRetrieve one Tremendous campaign by ID.
INPUTS: id
create_orderWRITECreate a Tremendous reward order with an optional external ID for idempotent retries.
INPUTS: externalId / fundingSourceId / campaignId / products / value
generate_reward_linkREVIEWGenerate a redemption link for an existing Tremendous reward.
INPUTS: id
get_funding_sourceREADRetrieve one Tremendous funding source by ID, including the special BALANCE value.
INPUTS: id
get_orderREADRetrieve one Tremendous order by ID or external ID.
INPUTS: id
get_productREADRetrieve one Tremendous product by ID.
INPUTS: id
get_rewardREADRetrieve one Tremendous reward by ID.
INPUTS: id
list_campaignsREADList Tremendous campaigns in the current organization.
list_funding_sourcesREADList funding sources in the current Tremendous organization.
list_ordersREADList Tremendous orders with optional pagination and order filters.
INPUTS: offset / limit / campaignId / externalId / createdAtGte
list_organizationsREADList the Tremendous organization tied to the current API key.
list_productsREADList Tremendous products with optional country, currency, and subcategory filters.
INPUTS: country / currency / subcategory
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign
idOPTIONAL- The Tremendous campaign ID.
create_order
externalIdOPTIONAL- A customer-supplied idempotency reference for this order.
fundingSourceIdREQUIRED- The Tremendous funding source ID used to pay for the order. Use balance to use the Tremendous balance.
campaignIdOPTIONAL- The Tremendous campaign ID that defines the reward experience.
productsOPTIONAL- Product IDs that the recipient can choose from. This overrides campaign products when provided.
valueREQUIRED- The monetary value of the Tremendous reward.
generate_reward_link
idOPTIONAL- The Tremendous reward ID.
get_funding_source
idOPTIONAL- The Tremendous funding source ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign
Retrieve one Tremendous campaign by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_campaignControl Create Order
Create a Tremendous reward order with an optional external ID for idempotent retries. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_orderVerify with Get Funding Source
Retrieve one Tremendous funding source by ID, including the special BALANCE value. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_funding_sourceSAFETY BOUNDARY
Operate Tremendous with explicit limits
- Authorize Tremendous with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Tremendous rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Tremendous task completed successfully.
CONNECTION MODEL
API key
Tremendous API key used as a Bearer token. In production, create it from Team settings -> Developers after API access is approved: https://developers.tremendous.com/docs/production-api-access.
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
- 11
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 Tremendous.