Integration
Connect wethod to Kiflo PRM
When New Client fires in wethod, your agent runs Add Partner to Existing Deal in Kiflo PRM. 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 wethod and Kiflo PRM 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 wethod can start in Kiflo PRM
When New Client in wethod
then Add Partner to Existing Deal in Kiflo PRM
When New Contact in wethod
then Create Contact in Kiflo PRM
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 wethod and Kiflo PRM
Triggers and actions 7 triggers · 90 actions
Trigger
New ClientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Trigger
New ContactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Trigger
New InvoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Trigger
New PersonHere the dedicated support page.
Trigger
New ProjectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Trigger
Sent InvoiceTriggers when an invoice is in sent status.
Trigger
Updated ProjectTriggers when a project is created or updated.
Action
Archive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Create a clientRequired permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.
Action
Create a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Create an invoiceRequired permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.
Action
Create a personCreates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/
Action
Create a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Create a projectRequired permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met
Action
Create a project statusRequired permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.
Action
Create a timesheetRequired permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Delete a clientRequired permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.
Action
Delete a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Delete an invoiceRequired permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.
Action
Delete a person allocationRequired permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He
Action
Delete a projectRequired permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.
Action
Delete a timesheetRequired permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.
Action
Find ClientFinds the first client whose name matches the search text.
Action
Find PersonFinds the first person whose name or email matches the search text.
Action
Get a budgetRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
Get a clientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
Get a contactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
Get an expenseRequired permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.
Action
Get an invoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.
Action
Get a personHere the dedicated support page.
Action
Get a projectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
Get a stream:::warning Requires **Streams** to be enabled in company settings. :::
Action
Get the authenticated personReturns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.
Action
List budgetsRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
List business unitsRequired permissions: - **settings.company**: allows view of company business units.
Action
List clientsRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
List contactsRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
List expensesRequired permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.
Action
List invoicesRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Action
List job titlesRequired permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.
Action
List people allocationsRequired permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.
Action
List personsHere the dedicated support page.
Action
List projectsThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
List project statusesRequired permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.
Action
List project typesList project types
Action
List streams:::warning Requires **Streams** to be enabled in company settings. :::
Action
List timesheetsRequired permissions: - **timetracking.view** Here the dedicated support page.
Action
Set an invoice as paidRequired permissions: - **invoices.edit_sent**: allows setting invoices as paid.
Action
Set an invoice as unpaidRequired permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.
Action
Unarchive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Update a clientRequired permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.
Action
Update a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Update an invoiceRequired permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.
Action
Update a personRequired permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.
Action
Update a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Update a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].
Action
Update a timesheetRequired permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Accept a Partner ApplicationAccepts a pending partner application, which turns the applicant into a partner, and returns the updated application. Can also give the partner access to the Kiflo partner portal.
Action
Accept DealAccepts a deal in Kiflo and sets its status to Accepted, optionally adding a note.
Action
Accept LeadAccepts a lead in Kiflo and sets its status to Accepted, optionally adding a note.
Action
Add Partner to Existing DealAdds a partner with a specific role to an existing deal, making the deal available to that partner in their partner portal. Returns the new deal partner record.
Action
Associate Customer to DealLinks a customer to an existing deal — either an existing customer by ID, or a new customer created from the details you supply.
Action
Convert Lead to CustomerConverts a lead into a customer and marks the lead as Converted, returning the updated lead.
Action
Convert Lead to DealConverts a lead into a deal and sets the lead's status to Converted. Returns the updated lead, including the id of the new deal.
Action
Create AttachmentDownloads a file from a URL and attaches it to a Kiflo partner, deal, lead, note, payout, customer or collaboration.
Action
Create Channel ConflictRecords a channel conflict detected in an external source, such as your CRM, and makes it visible in Kiflo. Returns the created channel conflict.
Action
Create ContactCreates a new contact in Kiflo with the contact properties you provide. Contacts must be associated with deals to be visible.
Action
Create CustomerCreates a new customer in Kiflo, with your customer properties, and optionally associates it with a partner.
Action
Create DealCreates a new deal in Kiflo, optionally linking a contact, partners and custom deal properties.
Action
Create LeadCreates a lead in Kiflo, optionally assigning it to a partner or recording the partner who sourced it.
Action
Create NoteCreates a note on an existing partner, lead, deal, customer or payout in Kiflo.
Action
Create PartnerCreates a new partner in Kiflo, optionally with its main contact, group, program level, onboarding stage and payout details.
Action
Create RewardCreates a reward for a partner in Kiflo, such as a gift card or coupon.
Action
Create TransactionCreates a transaction in Kiflo for an existing customer, optionally linked to a partner and a deal, and returns the new transaction.
Action
Find a CertificationReturns the certifications defined in your Kiflo account whose name contains the text you specify.
Action
Find a ContactReturns the contacts whose chosen property exactly matches the value you specify.
Action
Find a CustomerReturns the customers that match a condition on a customer field or custom property, newest first.
Action
Find a DealReturns the deals that match a condition you choose, such as a status, partner, customer, amount or custom property, newest first, along with the total number of matches.
Action
Find a LeadReturns the leads that match a search condition, newest first, along with the total number of matches.
Action
Find a PartnerReturns the partners that match a search on a partner field or one of your own partner properties, such as name, status or main contact email.
Action
Find a Partner ApplicationReturns the partner applications that match a partner name, team member email, status or partner.
Action
Find a Partner Team MemberReturns the partner team members that match an email address, a partner, or both.
Action
Find a PayoutReturns the payouts that match a condition you choose, such as a status, partner, amount or date, newest first.
Action
Find a TransactionReturns the transactions that match the search conditions you set, newest first, with the total number of matches.
Action
Give a CertificationGives a certification to a partner team member and returns the resulting certification record, including its status and expiration date.
Action
Invite Team MemberSends a partner team member an email inviting them to join the partner portal, and returns the team member with their invitation link. No email goes out if the team member was already invited.
Action
Pay PayoutMarks a validated payout as paid in Kiflo and returns the updated payout. This records the payment and does not move any money.
Action
Refuse DealRefuses a deal in Kiflo and sets its status to Refused, optionally adding a note. Returns the refused deal.
Action
Refuse LeadRefuses a lead in Kiflo and sets its status to Refused, optionally adding a note. Returns the updated lead.
Action
Reject a Partner ApplicationRejects a partner application that is still pending, so the applicant does not become a partner. Returns the rejected application.
Action
Start Partner OnboardingStarts onboarding for a partner by moving them into the chosen onboarding pipeline, optionally at a specific stage. Returns the updated partner.
Action
Update CustomerUpdates an existing customer in Kiflo, changing only the properties, status, source or partner you supply. Returns the updated customer.
Action
Update DealUpdates an existing deal in Kiflo, changing only the details you supply, and returns the updated deal.
Action
Update LeadUpdates an existing lead's deadline, currency, assigned partner contact, owner and properties, and returns the updated lead.
Action
Update PartnerUpdates an existing partner in Kiflo. Only the values you supply change; everything else on the partner stays as it is.
Action
Update PayoutUpdates the name and properties of an existing payout. Properties left blank are not changed. Returns the updated payout.
Action
Validate PayoutValidates a payout, optionally asking the partner to validate all its rewards and/or attach an invoice. Returns the validated payout.
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 wethod
wethod to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
wethod to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
wethod to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
wethod to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
wethod to AnthropicAnthropic builds Claude, a family of large language models.
wethod to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
More into Kiflo PRM
HubSpot to Kiflo PRMHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Kiflo PRMSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Kiflo PRMSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Kiflo PRMGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Kiflo PRMGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Kiflo PRMGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
wethod and Kiflo PRM, answered
What can start an automation from wethod?
Any of wethod's 7 triggers in the catalog, including New Client, New Contact, New Invoice and New Person. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Kiflo PRM when something happens in wethod?
Any of Kiflo PRM's 40 actions, including Create Attachment, Create Channel Conflict, Create Contact and Create Customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Kiflo PRM to wethod?
Kiflo PRM has no triggers in the catalog today, so automations start in wethod. If you need the other direction, ask: your agent reads Kiflo PRM's API documentation and adds it.
Do I have to build a connector for wethod or Kiflo PRM?
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 wethod and Kiflo PRM 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.