Integration
Connect HelpCrunch and Pipefy
When Chat Assignee Updated fires in HelpCrunch, your agent runs Create Record in Pipefy, or Moved Card in Pipefy to Add Customer Event in HelpCrunch. 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 HelpCrunch and Pipefy 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 HelpCrunch and Pipefy can do together
From HelpCrunch to Pipefy
When Chat Assignee Updated in HelpCrunch
then Create Record in Pipefy
When Chat Status Updated in HelpCrunch
then Update Database Record in Pipefy
From Pipefy to HelpCrunch
When Moved Card in Pipefy
then Add Customer Event in HelpCrunch
When New Card in Pipefy
then Send Message in HelpCrunch
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 HelpCrunch and Pipefy
Triggers and actions 14 triggers · 30 actions
Trigger
Chat Assignee UpdatedTriggers when a HelpCrunch chat is assigned to a different agent.
Trigger
Chat ClosedTriggers when a HelpCrunch chat is closed.
Trigger
Chat Status UpdatedTriggers when a HelpCrunch chat's status changes.
Trigger
Customer Email UpdatedTriggers when a HelpCrunch customer's email changes.
Trigger
Customer Tags UpdatedTriggers when a HelpCrunch customer's tags change.
Trigger
Customer UnsubscribedTriggers when a HelpCrunch customer unsubscribes.
Trigger
New Chat CreatedTriggers when a new chat is created in HelpCrunch.
Trigger
New Customer CreatedTriggers when a new customer is created in HelpCrunch.
Action
Add Customer EventRecords a custom event against a HelpCrunch customer.
Action
Assign ChatAssigns a HelpCrunch chat to an agent.
Action
Create ChatCreates a HelpCrunch chat with a customer.
Action
Delete CustomerDeletes a HelpCrunch customer.
Action
Find ChatsFinds HelpCrunch chats whose field matches a value, such as the customer email or status.
Action
Find CustomerFinds HelpCrunch customers whose field matches a value, such as by email.
Action
Get ChatReturns one HelpCrunch chat by ID.
Action
Get CustomerReturns one HelpCrunch customer by ID.
Action
Get OrganizationReturns the HelpCrunch organization and whether the team is online.
Action
List AgentsReturns the agents in the HelpCrunch account.
Action
List ApplicationsReturns the HelpCrunch applications (website widget, mobile apps and messenger channels).
Action
List Chat MessagesReturns the messages of a HelpCrunch chat, newest first.
Action
List DepartmentsReturns the HelpCrunch departments and their agents.
Action
Send MessagePosts a message or private note into a HelpCrunch chat.
Action
Snooze ChatSnoozes a HelpCrunch chat until a time.
Action
Tag CustomerAdds tags to a HelpCrunch customer; unknown tags are created.
Action
Untag CustomerRemoves tags from a HelpCrunch customer.
Action
Update Chat DepartmentMoves a HelpCrunch chat to a department.
Action
Update Chat StatusChanges a HelpCrunch chat's status, such as closing it.
Trigger
Done CardTriggers when a card is done.
Trigger
Moved CardTriggers when a card is moved.
Trigger
New CardTriggers when a new card is created.
Trigger
New Database RecordTriggers when a new record is created.
Trigger
Updated Card FieldTriggers when a card field is updated.
Trigger
Updated Record FieldTriggers when a record field is updated.
Action
Create CardCreates a card in a Pipefy pipe, filling in its start form fields.
Action
Create RecordCreates a new table record.
Action
Delete CardPermanently deletes a card from its pipe.
Action
Delete Database RecordDelete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
Action
Find CardReturns the cards in a pipe whose chosen field matches the specified value.
Action
Find Database RecordsFind a database records by title.
Action
Get CardRetrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
Action
Get Database RecordFetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
Action
Move CardMoves a Pipefy card to another phase of its pipe.
Action
Update Card FieldSets a new value on one field of an existing Pipefy card.
Action
Update Database RecordUpdate a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.
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 HelpCrunch
HelpCrunch to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
HelpCrunch to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
HelpCrunch to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
HelpCrunch to MailchimpMailchimp marketing automation and email platform.
HelpCrunch to StripeStripe is a payment processing platform for online businesses.
HelpCrunch to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Pipefy
GrowSurf to PipefyGrowSurf is referral software for B2C and B2B tech companies.
HubSpot to PipefyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PipefyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PipefyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PipefyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
HelpCrunch and Pipefy, answered
What can start an automation from HelpCrunch?
Any of HelpCrunch's 8 triggers in the catalog, including Chat Assignee Updated, Chat Status Updated, Customer Email Updated and Customer Tags Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefy when something happens in HelpCrunch?
Any of Pipefy's 11 actions, including Create Card, Create Record, Update Card Field and Update Database Record. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefy to HelpCrunch?
Yes. When something happens in Pipefy, your agent can act in HelpCrunch too. This page covers both directions: Pipefy's triggers and HelpCrunch's actions are listed here as well.
Do I have to build a connector for HelpCrunch or Pipefy?
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 HelpCrunch and Pipefy 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.