Integration
Connect Lemcal and Process Street
When New Meeting fires in Lemcal, your agent runs Add one-off task in Process Street, or Data Set Record Created in Process Street to Get Meeting Type in Lemcal. 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 Lemcal and Process Street 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 Lemcal and Process Street can do together
From Lemcal to Process Street
When New Meeting in Lemcal
then Add one-off task in Process Street
From Process Street to Lemcal
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 Lemcal and Process Street
Triggers and actions 8 triggers · 28 actions
- New Meeting
Triggers when a new meeting is booked in your lemcal calendar.
- Get Meeting Type
Returns one meeting type by its ID, with its name, duration and booking slug.
- List Meetings
Returns your booked meetings, optionally only those of one meeting type.
- List Meeting Types
Returns all of your meeting types.
- Data Set Record Created
Triggers when a new record is added to a data set.
- Data Set Record Updated
Triggers when an existing record is updated in a data set.
- New Comment
Triggers when a new comment is posted on a task in a workflow, or in a specific workflow run.
- New Comment Attachment
Triggers when someone attaches a file to a comment in a workflow run.
- New Task Checked
Triggers when a task is checked off in a workflow.
- New Workflow Run
Triggers when a workflow is run.
- Task Ready
Triggers when a task is ready to be worked on.
- Add comment
Adds a comment to a task in a Process Street workflow run.
- Add one-off task
Creates a one-off task in Process Street, optionally linked to a workflow run, with assignees and subtasks.
- Assign user to task
Assigns a user, by email address, to a task in a workflow run. An email that is not an organization member is invited as a guest.
- Complete one-off task
Marks a one-off task as completed and returns the updated task.
- Create Data Set Record
Adds a new record to a data set.
- Delete Data Set Record
Deletes an existing record in a data set.
- Delete workflow run
Deletes a workflow run in Process Street. It can be restored later with Undelete.
- Find Data Set Records
Search for data set records by form fields.
- Find Workflow Run
Search for a workflow run by ID, name, form fields, and other attributes.
- Get data set record
Returns one record from a Process Street data set, including its field values.
- Get task
Returns a task in a workflow run, including its status, due date, completion details and whether it is hidden or stopped.
- Get workflow
Returns a workflow (template) by its ID, including its name, folder, sharing settings and audit details.
- Get workflow run
Returns a workflow run (one execution of a workflow) by its ID, including its name, status, due date and workflow.
- List comments
Returns the comments on a workflow, or on a workflow run (optionally narrowed to one task), newest first.
- List data sets
Returns the data sets in your Process Street organization, including each data set's name and column definitions.
- List form fields
Returns the form fields defined in a Process Street workflow, with each field's type, label, key and task.
- List form field values
Returns every form field value filled in on a workflow run, with each field's label, key, type and value.
- List users
Returns the users in your Process Street organization, including deactivated ones, with their email, name and membership status.
- List Workflow Run Tasks
lists all tasks (id, name, status, dueDate) in one workflow run. Read-only; supplies the task id the Update Task action needs.
- List Workflows
Lists the workflows in your Process Street organization.
- Run Workflow
Runs a workflow.
- Update Data Set Record
Updates an existing record in a data set.
- Update form field values
Sets the values of one or more form fields in a Process Street workflow run, leaving other fields unchanged.
- Update Task
Update a task in a workflow run.
- Update Workflow Run
Update an existing workflow run.
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 Lemcal
Lemcal to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Lemcal to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Lemcal to MailchimpMailchimp marketing automation and email platform.
Lemcal to StripeStripe is a payment processing platform for online businesses.
Lemcal to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Lemcal to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Process Street
HubSpot to Process StreetHubSpot is your all-in-one stop for all of your marketing software needs.
Google Calendar to Process StreetGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Process StreetGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Pipedrive to Process StreetPipedrive is a sales CRM and pipeline management tool.
ActiveCampaign to Process StreetActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Lemcal and Process Street, answered
What can start an automation from Lemcal?
Any of Lemcal's 1 trigger in the catalog, including New Meeting. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Process Street when something happens in Lemcal?
Any of Process Street's 25 actions, including Create Data Set Record, Update Data Set Record, Update form field values and Update Task. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Process Street to Lemcal?
Yes. When something happens in Process Street, your agent can act in Lemcal too. This page covers both directions: Process Street's triggers and Lemcal's actions are listed here as well.
Do I have to build a connector for Lemcal or Process Street?
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 Lemcal and Process Street 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.