Raisely MCP integration for AI agents.
Connect AI agents to Raisely through 8 structured actions, including get campaign, create webhook, and delete webhook. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 8
- 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 Raisely integration exposes
The Raisely Agent App exposes 8 provider-backed actions for finance and marketing work. Its current contract lets an authorized agent fetch one raisely campaign by uuid, path, or domain, create a raisely webhook for account-wide or campaign-specific events, and delete a raisely webhook and return the deleted record. 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 Raisely account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Raisely capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaignREADFetch one Raisely campaign by UUID, path, or domain.
INPUTS: campaign / private / pruneConfig / includeTags
create_webhookWRITECreate a Raisely webhook for account-wide or campaign-specific events.
INPUTS: campaignUuid / events / secret / url
delete_webhookHIGH IMPACTDelete a Raisely webhook and return the deleted record.
INPUTS: webhookId
get_profileREADFetch one Raisely fundraising profile by UUID or path.
INPUTS: profilePath / campaign / private
list_campaignsREADList Raisely campaigns with optional search, filters, sorting, and pagination.
INPUTS: private / query / limit / offset / sort
list_profilesREADList fundraising profiles in a Raisely campaign.
INPUTS: campaign / private / query / limit / offset
list_webhooksREADList webhooks configured for a Raisely campaign.
INPUTS: campaign / private / query / limit / offset
update_webhookWRITEUpdate a Raisely webhook's events, secret, or destination URL.
INPUTS: webhookId / private / events / secret / url
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign
campaignREQUIRED- The campaign UUID, path, or domain.
privateOPTIONAL- Whether Raisely should include private campaign fields.
pruneConfigOPTIONAL- Whether to omit the large campaign config from the result.
includeTagsOPTIONAL- Whether to include tags attached to the campaign.
create_webhook
campaignUuidOPTIONAL- The campaign UUID to restrict events to, or omit it for account-wide events.
eventsOPTIONAL- The Raisely event names to forward to the webhook.
secretOPTIONAL- The shared secret Raisely includes in webhook payloads.
urlOPTIONAL- The URL Raisely should send webhook events to.
delete_webhook
webhookIdREQUIRED- The Raisely webhook UUID.
get_profile
profilePathREQUIRED- The profile UUID or path.
campaignOPTIONAL- The campaign UUID, path, or domain used for lookup context.
privateOPTIONAL- Whether Raisely should include private profile fields.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign
Fetch one Raisely campaign by UUID, path, or domain. 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 Webhook
Create a Raisely webhook for account-wide or campaign-specific events. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_webhookVerify with Get Profile
Fetch one Raisely fundraising profile by UUID or path. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_profileSAFETY BOUNDARY
Operate Raisely with explicit limits
- Authorize Raisely with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_webhook` 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 Raisely rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Raisely task completed successfully.
CONNECTION MODEL
API key
Raisely campaign secret key used as a Bearer token. Create or view it in Raisely admin, and see the official developer portal at https://raisely.com/developers.
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
- 5
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
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 Raisely.