Gift Up MCP integration for AI agents.
Connect AI agents to Gift Up through 17 structured actions, including get company, reactivate gift card, and get gift card. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 17
- 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 Gift Up integration exposes
The Gift Up Agent App exposes 17 provider-backed actions for finance and marketing work. Its current contract lets an authorized agent get the gift up company associated with the api key, reactivate a voided gift up gift card, and get one gift up gift card by code. 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 Gift Up account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Gift Up capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_companyREADGet the Gift Up company associated with the API key.
reactivate_gift_cardREVIEWReactivate a voided Gift Up gift card.
INPUTS: code / reason / locationId / metadata
get_gift_cardREADGet one Gift Up gift card by code.
INPUTS: code
get_itemREADGet one Gift Up item by ID.
INPUTS: id
get_orderREADGet one Gift Up order by ID or order number.
INPUTS: id
get_report_transactionREADGet one Gift Up report transaction by ID.
INPUTS: id
list_gift_cardsREADList Gift Up gift cards with optional filters.
INPUTS: status / createdOnOrAfter / updatedOnOrAfter / orderId / sku
list_itemsREADList Gift Up items, optionally filtered by item group.
INPUTS: groupId
list_locationsREADList Gift Up account locations.
list_ordersREADList Gift Up orders with optional filters.
INPUTS: createdOnOrAfter / purchaserEmail / source / limit / offset
list_promotionsREADList Gift Up promotions.
list_report_transactionsREADList Gift Up report transactions with optional filters.
INPUTS: eventOccurredOnOrAfter / eventOccurredOnOrBefore / events / users / locations
INPUT CONTRACTS
Know what the action needs before it runs.
reactivate_gift_card
codeREQUIRED- The Gift Up gift card code.
reasonOPTIONAL- The reason to record in the Gift Up history log.
locationIdOPTIONAL- The Gift Up location ID where the event occurred.
metadataOPTIONAL- Metadata key-value pairs to attach to the Gift Up event.
get_gift_card
codeOPTIONAL- The Gift Up gift card code.
get_item
idOPTIONAL- The Gift Up object ID.
get_order
idOPTIONAL- The Gift Up order ID or order number.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company
Get the Gift Up company associated with the 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_companyVerify with Get Gift Card
Get one Gift Up gift card by code. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_gift_cardSAFETY BOUNDARY
Operate Gift Up with explicit limits
- Authorize Gift Up with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Gift Up data may still be sensitive and should be minimized before it enters model context.
- 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 Gift Up rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Gift Up task completed successfully.
CONNECTION MODEL
API key
Gift Up API key sent as a Bearer token in the Authorization header. Create or view API keys in the Gift Up dashboard: https://giftup.app/integrations/api-keys.
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
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 6
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 Gift Up.