Integration
Connect Ploomes to ManyRequests
When New contact fires in Ploomes, your agent runs Add invoice in ManyRequests. 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 Ploomes and ManyRequests 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 Ploomes can start in ManyRequests
When New contact in Ploomes
then Add invoice in ManyRequests
When New deal in Ploomes
then Create Client in ManyRequests
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 Ploomes and ManyRequests
Triggers and actions 3 triggers · 46 actions
Trigger
New contactTriggers when a new contact (person or company) is created in Ploomes.
Trigger
New dealTriggers when a new deal is created in Ploomes.
Trigger
New taskTriggers when a new task is created in Ploomes.
Action
Add contactCreates a contact (a person or a company) in Ploomes and returns the new contact record.
Action
Add dealCreates a deal in Ploomes for a client, with its title, stage, owner, amount and custom field values.
Action
Add interaction recordCreates an interaction record (a note, call or email log) on a Ploomes contact or deal.
Action
Add productCreates a product in your Ploomes account and returns the new product.
Action
Add quoteCreates a quote (proposal) on a deal in Ploomes from a document template, optionally with product sections and custom field values.
Action
Add taskCreates a task in Ploomes, optionally linked to a contact or deal.
Action
Delete contactDeletes a contact (person or company) from your Ploomes account.
Action
Delete dealDeletes a deal from your Ploomes account.
Action
Find contacts by criteriaReturns the Ploomes contacts (people and companies) that match the criteria you give.
Action
Find deals by criteriaReturns the deals that match the criteria you give, such as a title, stage or customer.
Action
Find interaction records by criteriaReturns the interaction records (activity history entries) that match the criteria you give.
Action
Find tasks by criteriaReturns the tasks that match the criteria you specify, such as title, contact or deal.
Action
Finish taskMarks a Ploomes task as finished.
Action
Get quoteReturns a single quote (proposal) by its ID, including its custom field values.
Action
Lose dealMarks a Ploomes deal as lost with the chosen loss reason and returns the updated deal.
Action
Update contactUpdates an existing Ploomes contact (person or company). Only the fields you fill in are changed.
Action
Update dealUpdates an existing deal in Ploomes. Only the fields you fill in are changed.
Action
Update taskUpdates an existing task in Ploomes. Only the fields you fill in are changed.
Action
Win dealMarks a Ploomes deal as won and returns the updated deal.
Action
Add invoiceAdds a new invoice for a client from catalog services, pricing variations or custom line items, and returns the new invoice's id. The invoice is emailed to the client unless it is created as a draft.
Action
Add organizationCreates a new organization in your ManyRequests portal along with its owner client user. Returns the organization that was added.
Action
Add organization memberAdds a member to an organization, creating a new client user if no user with that email exists yet.
Action
Add subscription to organizationAdds a recurring service subscription to a client organization and returns the new subscription.
Action
Add time entryLogs time worked on a request for a team member, from a start time to an end time.
Action
Cancel Client SubscriptionCancels an active recurring service subscription belonging to a client organization.
Action
Create ClientCreates a client user in a ManyRequests organization. If a user with the email already exists, they are added to the organization.
Action
Create CommentAdds a comment to a request, posted as the chosen user, optionally internal-only or scheduled for later delivery.
Action
Create organization brandCreates a new brand within an organization.
Action
Create RequestCreates a new service request for a client under one of your services, with an optional description, priority, status, due date, brand, assignees and tags.
Action
Delete clientDeletes a client and removes them from their organization. A client who is the sole owner of an organization with active subscriptions cannot be deleted.
Action
Delete organizationDeletes an organization and all of its members from your ManyRequests portal.
Action
Delete requestDeletes a request in ManyRequests.
Action
Find Comments for RequestReturns the comments on a ManyRequests request, optionally limited to internal or non-internal comments.
Action
Find OrganizationFinds organizations whose name, owner name or owner email matches the search text, optionally narrowed by tags or subscription status.
Action
Find RequestReturns the service requests that match your search text or filters, such as status, priority, client, organization, assignee or request number.
Action
Get clientReturns a single client by ID, including their name, email and organization.
Action
Get invoiceReturns a single invoice with its status, number, notes, payment details and dates, optionally with its line items, taxes, client, coupon and payment gateway.
Action
Get organizationReturns a single organization by its ID, with its name, logo and dates, plus any related records you ask to include. An error occurs if the organization is not found.
Action
Get requestReturns a single service request by its ID or slug, with optional related records such as status, client, service, tags and form fields.
Action
List clientsReturns the clients in your ManyRequests portal, with optional search, organization filter and sorting.
Action
List servicesReturns the services offered in your ManyRequests portal, optionally filtered by search text, type, allocation or sale status.
Action
List team membersReturns the portal admins, admins and team members in your ManyRequests portal, optionally filtered by email or role.
Action
Update clientUpdates a client's name and/or email address.
Action
Update organizationUpdates the name of an existing organization and returns the updated organization.
Action
Update RequestUpdates an existing request's title, description, priority, status, due date, brand, assignees, tags or form fields.
Action
Update Request StatusMoves a ManyRequests request to a different status.
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 Ploomes
Ploomes to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Ploomes to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Ploomes to StripeStripe is a payment processing platform for online businesses.
Ploomes to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Ploomes to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Ploomes to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into ManyRequests
HubSpot to ManyRequestsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ManyRequestsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ManyRequestsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ManyRequestsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ManyRequestsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ManyRequestsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Ploomes and ManyRequests, answered
What can start an automation from Ploomes?
Any of Ploomes's 3 triggers in the catalog, including New contact, New deal and New task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in ManyRequests when something happens in Ploomes?
Any of ManyRequests's 27 actions, including Create Client, Create Comment, Create organization brand and Create Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ManyRequests to Ploomes?
ManyRequests has no triggers in the catalog today, so automations start in Ploomes. If you need the other direction, ask: your agent reads ManyRequests's API documentation and adds it.
Do I have to build a connector for Ploomes or ManyRequests?
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 Ploomes and ManyRequests 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.