Build solutions, not workarounds.
What do you want Pipefile and Lark to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Pipefile can start in Lark
When File Request Created in Pipefile
then Create New Lark Calendar Event in Lark
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 Pipefile and Lark
Triggers and actions 1 trigger · 22 actions
- File Request Created
Triggers when a file request is created.
- Add File Request From Template
Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
- Create Contact
Add to contacts
- Delete Contact
Delete a contact by id. Returns 204 No Content on success.
- Get Contact
Retrieve one contact by id.
- Get File Request
Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.
- List Contacts
Retrieve a paginated list of contacts, filterable by name/email/phone partial match.
- List File Request Templates
Retrieve the list of file request templates available for creating new file requests, with optional name search.
- Search File Requests
Finds all file requests matching this search query (contact name, email, tags, etc).
- Send Request
Create and send a new request
- Update Contact
Update name/email/phone of an existing contact by id.
- Create New Lark Calendar Event
Creates a new Lark Calendar event
- Create New Lark Folder
Creates a new empty folder inside a parent folder in Lark Drive (My Space).
- Create New Lark Task
Crreates a new task in Lark
- Search Lark Base
Searches a Lark Base table for records matching a filter. Returns up to 500 matching records.
- Search Lark Calendar Event
Searches events on a Lark calendar by keyword in the event title, optionally narrowed by time range, attendees, meeting rooms or group chats.
- Search Lark Docs
Searches the connected user's Lark documents by keyword, optionally narrowed to specific owners or group chats.
- Search Lark Sheets
Searches the connected user's Lark Docs space for spreadsheets (Sheets) whose title or content matches a keyword.
- Search Lark Task by Complete Status
Returns up to 100 of the connected user's own tasks that are either completed or not completed.
- Search Task by GUID
Looks up a single Lark task by its GUID and returns its full details: summary, description, dates, members, status and custom field values.
- Search Users in Lark
Searches the people in your Lark organization by name, as the connected user, and returns the matches.
- Update Existing Lark Task
Updates an existing task in Lark
- Update Lark Calendar Event
Updates an existing Lark Calendar event
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 Pipefile
Pipefile to Google AnalyticsGoogle Analytics tracks and reports website traffic, user behavior, and conversion data, enabling marketers...
Pipefile to ChannelsChannels is a data-driven phone system that lets you make and take calls directly in the browser.
Pipefile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipefile to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pipefile to StripeStripe is a payment processing platform for online businesses.
Pipefile to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Lark
HubSpot to LarkHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LarkGoogle Sheets
Gmail to LarkGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LarkGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipefile and Lark, answered
What can start an automation from Pipefile?
Any of Pipefile's 1 trigger in the catalog, including File Request Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Lark when something happens in Pipefile?
Any of Lark's 12 actions, including Create New Lark Calendar Event, Create New Lark Folder, Create New Lark Task and Update Existing Lark Task. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Lark to Pipefile?
Lark has no triggers in the catalog today, so automations start in Pipefile. If you need the other direction, ask: your agent reads Lark's API documentation and adds it.
Do I have to build a connector for Pipefile or Lark?
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.
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.