Integration
Connect COR to Flodesk
When Create Brand fires in COR, your agent runs Find a Subscriber by Email Address in Flodesk. 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 COR and Flodesk to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 COR can start in Flodesk
When Create Brand in COR
then Find a Subscriber by Email Address in Flodesk
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 COR and Flodesk
Triggers and actions 12 triggers · 39 actions
- Create Brand
Triggers when a new brand is created in COR.
- Create Client
Triggers when a new client is created in COR.
- Create Hour
Triggers when a new time entry is logged in COR.
- Create Invoice
Triggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart.
- Create Product
Triggers when a new product is created in COR.
- Create Project
Triggers when a new project is created in COR.
- Create Task
Triggers when a new task is created in COR. Returns the new task's details.
- Create User
Triggers when a new user is created in COR.
- Updated Client
Triggers when an existing client is changed in COR.
- Updated Project
Triggers when an existing project is updated in COR.
- Updated Task
Triggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears.
- Updated User
Triggers when a user in COR is created or changed, such as their name, email, role, position or labels.
- Add brand
Creates a new brand under a client in COR.
- Add team
Creates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created.
- Create Client
Creates a new client in COR with its company details and primary contact, and returns the new client's id.
- Create Fee
Creates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee.
- Create Hour
Logs a time entry against a task in COR and returns the new entry's id.
- Create Invoice
Creates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction.
- Create Project
Creates a new project for a client in COR and returns the created project.
- Create Task
Creates a new task in COR, optionally within a project, and returns the created task.
- Delete Project
Deletes a project in COR by its ID.
- Delete task
Deletes a task in COR by its ID.
- Find clients by name
Returns the clients whose name matches the specified name.
- Find projects by name
Returns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details.
- Get client
Returns a single COR client by its id, including its business name, contact details, website and description.
- Get project
Returns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found.
- Get task
Returns a single COR task by its id, including its title, project, deadline, status and priority.
- List clients
Returns all clients in the COR account, optionally narrowed by filter criteria.
- List fees
Returns the fees in the COR account, including each fee's name, estimate, status and dates.
- List hours
Returns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose.
- List products
Returns all products in the COR account, each with its name, client and brand.
- List projects
Returns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state.
- List tasks
Returns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose.
- List teams
Returns the teams in the COR workspace, including each team's name and description.
- Update Project
Updates an existing project in COR, changing only the fields you fill in, and returns the updated project.
- Update Task
Updates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task.
- Add custom field
Creates a new subscriber custom field in your Flodesk account with the label you choose.
- Add Existing Subscriber to Segment
Adds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.
- Add Existing Subscriber to Workflow
Adds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.
- Add segment
Creates a new segment in your Flodesk account and returns it.
- Create/Update Subscriber
Creates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.
- Find a Subscriber by Email Address
Looks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.
- Get segment
Returns a single Flodesk segment, including its name, color, type and number of active subscribers.
- List campaigns
Returns the email campaigns in your Flodesk account, optionally filtered by status or a search term.
- List custom fields
Returns every subscriber custom field defined in your Flodesk account, with each field's key and display label.
- List segments
Returns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.
- List subscribers
Returns subscribers in your Flodesk account, optionally filtered by status or segment.
- List workflows
Returns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).
- Remove Existing Subscriber From Segment
Removes an existing Flodesk subscriber from one or more segments and returns the updated subscriber.
- Remove Existing Subscriber From Workflow
Removes an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.
- Unsubscribe Subscriber
Unsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.
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 COR
COR to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
COR to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
COR to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
COR to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
COR to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
COR to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Flodesk
Questions
COR and Flodesk, answered
What can start an automation from COR?
Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create Invoice. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Flodesk when something happens in COR?
Any of Flodesk's 15 actions, including Create/Update Subscriber, Add custom field, Add Existing Subscriber to Segment and Add Existing Subscriber to Workflow. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Flodesk to COR?
Flodesk has no triggers in the catalog today, so automations start in COR. If you need the other direction, ask: your agent reads Flodesk's API documentation and adds it.
Do I have to build a connector for COR or Flodesk?
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.
Can my AI client use COR and Flodesk without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.