---
title: "Connect folk and Jitbit Helpdesk - APIANT.ai"
description: "When \"Company Added\" fires in folk, your agent runs \"Add company\" in Jitbit Helpdesk, or \"New Ticket\" in Jitbit Helpdesk to \"Create Deal\" in folk."
canonical: "https://apiant.ai/connect/folk-to-jitbit-helpdesk"
---

# Connect folk and Jitbit Helpdesk

When **Company Added** fires in [folk](https://apiant.ai/connections/folk), your agent runs **Add company** in [Jitbit Helpdesk](https://apiant.ai/connections/jitbit-helpdesk), or **New Ticket** in Jitbit Helpdesk to **Create Deal** in folk. Describe the whole flow and it is built, tested on every scenario and kept running.

folk **11** triggers folk **16** actions Jitbit Helpdesk **1** trigger Jitbit Helpdesk **19** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want folk and Jitbit Helpdesk to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What folk and Jitbit Helpdesk can do together

### From folk to Jitbit Helpdesk

- When **Company Added** in folk then **Add company** in Jitbit Helpdesk
- When **Company Custom Field Updated** in folk then **Add tag to ticket** in Jitbit Helpdesk

### From Jitbit Helpdesk to folk

- When **New Ticket** in Jitbit Helpdesk then **Create Deal** in folk
- When **New Ticket** in Jitbit Helpdesk then **Create Note** in folk

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 folk and Jitbit Helpdesk

## Triggers and actions 12 triggers · 35 actions

- Trigger

**Company Added**

Triggers when a new company is created or added to a group.

- Trigger

**Company Custom Field Updated**

Triggers when a company custom field (for example tag, status, text, assignee) is updated.

- Trigger

**Company Removed**

Triggers when a company is deleted from the workspace or removed from a group.

- Trigger

**Company Updated**

Triggers when a company basic field (like name, email or URL) in a group is updated.

- Trigger

**Deal Added**

Fires when a new deal is created.

- Trigger

**Deal Removed**

Fires when a deal is deleted from a pipeline.

- Trigger

**Deal Updated**

Fires when a deal is updated (stage change, field update).

- Trigger

**Person Added**

Triggers when a new person is created or added to a group.

- Trigger

**Person Custom Field Updated**

Triggers when a person custom field (for example tag, status, text, assignee) is updated.

- Trigger

**Person Removed**

Triggers when a person is deleted from the workspace or removed from a group.

- Trigger

**Person Updated**

Triggers when a person basic field (like first name, job title, email or URL) in a group is updated.

- Action

**Create Company**

Creates a company in folk, optionally adding it to a group and setting that group's custom fields.

- Action

**Create Deal**

Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields.

- Action

**Create Group**

Creates a group in folk. A default "All people" table view is added to the group automatically.

- Action

**Create Note**

Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note.

- Action

**Create Person**

Creates a person in folk, optionally adding them to a group and setting that group's custom fields.

- Action

**Create Reminder**

Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule.

- Action

**Delete Company**

Deletes a company from folk by its id.

- Action

**Delete Person**

Deletes a person from folk by their id. This also removes their custom fields, notes and associations.

- Action

**Find a Company**

Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping.

- Action

**Find a Person**

Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping.

- Action

**Get a Company**

Fetches one folk company by id, including its custom field values.

- Action

**Get a Note**

Fetches one folk note by id, with its text, author and the record it is attached to.

- Action

**Get a Person**

Fetches one folk person by id, including their custom field values.

- Action

**List Groups**

Returns the groups in the folk workspace, with each group's id, name and visibility.

- Action

**Update Company**

Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list.

- Action

**Update Person**

Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list.

- Trigger

**New Ticket**

Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.

- Action

**Add article**

Creates a new knowledge base article in a category.

- Action

**Add asset**

Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.

- Action

**Add company**

Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.

- Action

**Add tag to ticket**

Adds a tag to a ticket. The tag is created if it does not already exist.

- Action

**Add time spent**

Logs a time spent entry on a ticket under the connected user. Requires technician permissions.

- Action

**Create New Reply**

Posts a new reply (comment) to an existing helpdesk ticket.

- Action

**Create Ticket**

Creates a new helpdesk ticket in a category, with a subject, body and priority.

- Action

**Create User**

Creates a new helpdesk user. Requires administrator permissions.

- Action

**Find Ticket**

Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.

- Action

**Find User**

Finds a helpdesk user by their email address and returns their profile.

- Action

**Get Article**

Returns a knowledge base article with its full content, category, tags and attachments.

- Action

**Get ticket**

Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.

- Action

**List Companies**

Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.

- Action

**List Ticket Comments**

Returns all comments (replies) posted on a Jitbit Helpdesk ticket.

- Action

**List tickets**

Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.

- Action

**List Time Spent Entries**

Returns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions.

- Action

**Update company**

Updates a company's name, notes and email domains in Jitbit Helpdesk.

- Action

**Update ticket**

Updates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body.

- Action

**Update user**

Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.

## Each app on its own

- [ **folk** folk is the next generation CRM for teams](https://apiant.ai/connections/folk)
- [ **Jitbit Helpdesk** A great help desk app for small and medium sized companies.](https://apiant.ai/connections/jitbit-helpdesk)

Reviews

## What our customers say

## More from folk

- [ **folk to OpenRouter** OpenRouter is a unified interface to AI models.](https://apiant.ai/connect/folk-to-openrouter)
- [ **folk to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/folk-to-hubspot)
- [ **folk to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/folk-to-salesforce)
- [ **folk to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/folk-to-slack)
- [ **folk to Google Sheets** Google Sheets](https://apiant.ai/connect/folk-to-google-sheets)
- [ **folk to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/folk-to-gmail)

## More into Jitbit Helpdesk

- [ **HubSpot to Jitbit Helpdesk** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-jitbit-helpdesk)
- [ **Google Sheets to Jitbit Helpdesk** Google Sheets](https://apiant.ai/connect/google-sheets-to-jitbit-helpdesk)
- [ **Gmail to Jitbit Helpdesk** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-jitbit-helpdesk)
- [ **Google Calendar to Jitbit Helpdesk** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-jitbit-helpdesk)
- [ **Google Drive to Jitbit Helpdesk** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-jitbit-helpdesk)
- [ **ActiveCampaign to Jitbit Helpdesk** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-jitbit-helpdesk)

Questions

## folk and Jitbit Helpdesk, answered

###

### What can start an automation from folk?

Any of folk's 11 triggers in the catalog, including Company Added, Company Custom Field Updated, Company Removed and Company Updated. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Jitbit Helpdesk when something happens in folk?

Any of Jitbit Helpdesk's 19 actions, including Create New Reply, Create Ticket, Create User and Update company. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Jitbit Helpdesk to folk?

Yes. When something happens in Jitbit Helpdesk, your agent can act in folk too. This page covers both directions: Jitbit Helpdesk's triggers and folk's actions are listed here as well.

###

### Do I have to build a connector for folk or Jitbit Helpdesk?

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 folk and Jitbit Helpdesk 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.
