Review a Campaign
Find campaigns and read one campaign’s detailed record.
/oo Raisely: List campaigns matching [query], get campaign [UUID or path] and summarize its returned information.
Use AI with Raisely to inspect fundraising campaigns and compare returned fundraising-profile information.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Find campaigns and read one campaign’s detailed record.
/oo Raisely: List campaigns matching [query], get campaign [UUID or path] and summarize its returned information.
List campaign profiles and inspect a selected profile.
/oo Raisely: List profiles in campaign [campaign], get profile [path] and compare the returned fundraising information.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Provide a Raisely Campaign Secret Key.
Connect Raisely →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Use AI with Raisely to inspect fundraising campaigns and compare returned fundraising-profile information.
Find campaigns and read one campaign’s detailed record.
List campaign profiles and inspect a selected profile.
List Raisely campaigns with optional search, filters, sorting, and pagination.
raisely.list_campaigns Fetch one Raisely campaign by UUID, path, or domain.
raisely.get_campaign List fundraising profiles in a Raisely campaign.
raisely.list_profiles Fetch one Raisely fundraising profile by UUID or path.
raisely.get_profile List webhooks configured for a Raisely campaign.
raisely.list_webhooks Create a Raisely webhook for account-wide or campaign-specific events.
raisely.create_webhook Update a Raisely webhook's events, secret, or destination URL.
raisely.update_webhook Delete a Raisely webhook and return the deleted record.
raisely.delete_webhook No matching tools.
Webhook actions can list, create, update or delete campaign or account-wide webhook subscriptions.
Their visibility depends on the secret key and requested private-data options.
Use a campaign UUID, path or domain, and a profile UUID or path where required. Private fields depend on connection permissions.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.