Integration
Connect LumApps and ProWorkflow Classic
When New Comment fires in LumApps, your agent runs Add Contact in ProWorkflow Classic, or New Company in ProWorkflow Classic to Create Comment in LumApps. 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 LumApps and ProWorkflow Classic 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 LumApps and ProWorkflow Classic can do together
From LumApps to ProWorkflow Classic
When New Comment in LumApps
then Add Contact in ProWorkflow Classic
From ProWorkflow Classic to LumApps
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 LumApps and ProWorkflow Classic
Triggers and actions 10 triggers · 36 actions
- New Comment
Triggers when a new comment is added to a LumApps content item or community post.
- New Community Post
Triggers when a new post is published in a LumApps community.
- New Notification
Triggers when the connected user receives a new LumApps notification.
- New Published Content
Triggers when a content item (page or news) is published in LumApps.
- New User
Triggers when a new user is added to the LumApps platform.
- Create Comment
Adds a comment, or a reply to a comment, on a LumApps content item or community post.
- Create Community Post
Creates a post in a LumApps community.
- Create Notification
Sends a custom in-app notification to a user or groups in LumApps.
- Delete Community Post
Deletes a LumApps community post.
- Delete Content
Deletes a LumApps content item (page or news).
- Find a Community
Finds communities whose title matches the search text and returns the first match.
- Get Community
Returns a LumApps community by its ID.
- Get Community Post
Returns a LumApps community post by its ID.
- Get Content
Returns a LumApps content item (page, news, article) by its ID.
- Get Group
Returns a LumApps user group by its ID.
- Get Site
Returns a LumApps site by its ID.
- Get User
Returns a LumApps user by email address or ID.
- Update Group Members
Adds users to and removes users from a LumApps group.
- New Company
Triggers when a new company is added in ProWorkflow.
- New Contact
Triggers when a new contact is added in ProWorkflow.
- New Project
Triggers when a new project is added in ProWorkflow.
- New Task
Triggers when a new task is added to a ProWorkflow project.
- New Time
Triggers when a new time record is logged in ProWorkflow.
- Add Client to Project
Adds a client contact to a project, keeping the project's existing contacts.
- Add Company
Creates a company (client, contractor, staff or other) in ProWorkflow.
- Add Contact
Creates a contact in ProWorkflow.
- Add Project
Creates a client project in ProWorkflow.
- Add Project Task
Creates a task in a ProWorkflow project.
- Add Time
Logs a time record against a ProWorkflow task.
- Delete Company
Deletes a company from ProWorkflow.
- Delete Contact
Deletes a contact from ProWorkflow.
- Delete Project
Deletes a project from ProWorkflow.
- Delete Task
Deletes a task from ProWorkflow.
- Find Client
Finds client companies in ProWorkflow matching a search term, name, code, email, tag or other filters, and returns the matching clients.
- Find Company
Returns a ProWorkflow company by its ID.
- Find Contact
Returns a ProWorkflow contact by its ID.
- Find Contractor
Finds contractor companies in ProWorkflow matching a name, code, email or search term, and returns the matching companies.
- Find Project
Returns a ProWorkflow project by its ID.
- Find Staff
Finds staff contacts in ProWorkflow by name, email, search term or other filters and returns the matching staff members.
- Find Task
Returns a ProWorkflow task by its ID.
- Make Task Active
Sets a ProWorkflow task's status to active.
- Update Company
Updates an existing company's details in ProWorkflow.
- Update Contact
Updates an existing contact in ProWorkflow.
- Update Contact Location
Updates the address (street, city, state, postal code and country) of an existing ProWorkflow contact.
- Update Project
Updates an existing project in ProWorkflow.
- Update Task
Updates an existing task in ProWorkflow, including marking it active or complete.
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 LumApps
LumApps to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LumApps to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LumApps to MailchimpMailchimp marketing automation and email platform.
LumApps to StripeStripe is a payment processing platform for online businesses.
LumApps to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LumApps to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into ProWorkflow Classic
HubSpot to ProWorkflow ClassicHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ProWorkflow ClassicGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ProWorkflow ClassicGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ProWorkflow ClassicGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ProWorkflow ClassicGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
LumApps and ProWorkflow Classic, answered
What can start an automation from LumApps?
Any of LumApps's 5 triggers in the catalog, including New Comment, New Community Post, New Notification and New Published Content. Describe the moment in plain language and your agent picks the right one.
What can your agent do in ProWorkflow Classic when something happens in LumApps?
Any of ProWorkflow Classic's 23 actions, including Update Company, Update Contact, Update Contact Location and Update Project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ProWorkflow Classic to LumApps?
Yes. When something happens in ProWorkflow Classic, your agent can act in LumApps too. This page covers both directions: ProWorkflow Classic's triggers and LumApps's actions are listed here as well.
Do I have to build a connector for LumApps or ProWorkflow Classic?
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 LumApps and ProWorkflow Classic 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.