Integration
Connect Cursion to Belong
When New Flow fires in Cursion, your agent runs Add ticket tier in Belong. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cursion and Belong to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cursion can start in Belong
When New Flow in Cursion
then Add ticket tier in Belong
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cursion and Belong
Triggers and actions 5 triggers · 37 actions
- New Flow
Triggers when a new Flow is created in your Cursion account.
- New Page
Triggers when a new page is added to a Cursion site.
- New Scan
Triggers when a new Scan is created for the selected Cursion page.
- New Site
Triggers when a new site is added to your Cursion account.
- New Test
Triggers when a new Test (a comparison of two scans) is created for a page.
- Add case
Generates a new test case for a site from a plain-language prompt and returns the process tracking its creation.
- Add flow
Creates a Flow in Cursion — a named sequence of steps (scans, cases, alerts) that FlowRuns execute.
- Create CaseRun
Runs a saved Case against a Site, creating a CaseRun that executes in the background and returns immediately.
- Create FlowRun
Runs a Flow against a Site and returns the new FlowRun, which completes asynchronously.
- Create Page
Creates a Page under a Cursion Site and, unless skipped, starts its initial baseline Scan.
- Create Scan
Starts a new Scan of a Site's pages in Cursion. The scan runs in the background and may take several minutes to complete.
- Create Site
Creates a Site in Cursion for a domain, then crawls it for pages and runs initial baseline scans in the background.
- Delete site
Deletes a site and, with it, all of the site's scans, tests, schedules and alerts.
- Get FlowRun
Returns a single FlowRun — the result of running a Flow against a Site — including its nodes, status and logs.
- Get scan
Returns a single Cursion scan with its HTML, logs, Lighthouse and security scores, and screenshots.
- Get site
Returns a single Cursion site with its URL, tags, crawl times and latest scan and test summary.
- Get test
Returns a single Test, the comparison of two scans of a page, with its scores, status and deltas.
- List flows
Returns the flows in your Cursion account, including each flow's steps (nodes) and connections (edges).
- List pages
Returns the pages that belong to a Cursion site, with each page's URL, tags and latest scan and test results.
- List scans
Returns the scans captured for a Cursion page, ordered by creation time.
- List sites
Returns the sites in your Cursion account, newest first, with each site's URL, tags and latest scan and test details.
- List tests
Returns the Tests run against a Cursion Page, ordered by creation time.
- Add hub
Creates a new hub (community group or NFT collection hub) owned by the connected user.
- Add note
Creates a note in a Belong hub with a title, description and content.
- Add ticket tier
Creates a priced ticket tier on a Belong event.
- Create Event
Creates a new event in Belong with its name, schedule, place and visibility settings, and returns the created event.
- Delete event
Deletes an event (activity) in Belong.
- Delete hub
Deletes a hub in Belong by its id or slug.
- Delete note
Deletes a note in Belong by its ID or slug.
- Delete ticket tier
Deletes a ticket tier from an event. Only tiers with no sold tickets and no attached NFT collection can be deleted.
- Find events nearby
Finds Belong events within the default radius of a latitude/longitude, optionally filtered by hub, owner, category, dates or a search term.
- Get event
Returns a single Belong event by its id or slug, including its schedule, place, and settings.
- Get hub
Returns a Belong hub by its id or public slug.
- Get note
Returns a single Belong note by its ID or slug, including its title, description, content and hub.
- Get user profile
Returns the profile of the Belong user whose account is connected: name, email, phone, username and biography.
- List events
Returns a list of Belong events, optionally filtered by hub, owner, category, dates or search text.
- List hubs
Returns a list of Belong hubs, optionally filtered by type, status, owner, member or search text.
- List ticket tiers
Returns an event's ticket tiers with inventory, pricing and the payment methods each tier can be bought with.
- Update event
Updates an existing Belong event's details such as name, description, dates, place, visibility and status. Only the fields you fill in are changed.
- Update hub
Updates an existing Belong hub's details, and can optionally connect existing events to it.
- Update note
Updates the title, description or content of an existing Belong note.
- Update ticket tier
Updates a ticket tier on an event: its name, description, card price, currency or capacity.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cursion
Cursion to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cursion to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cursion to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cursion to Google SheetsGoogle Sheets
Cursion to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cursion to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Belong
Questions
Cursion and Belong, answered
What can start an automation from Cursion?
Any of Cursion's 5 triggers in the catalog, including New Flow, New Page, New Scan and New Site. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Belong when something happens in Cursion?
Any of Belong's 20 actions, including Create Event, Update event, Update hub and Update note. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Belong to Cursion?
Belong has no triggers in the catalog today, so automations start in Cursion. If you need the other direction, ask: your agent reads Belong's API documentation and adds it.
Do I have to build a connector for Cursion or Belong?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.