---
title: "Connect Jitbit Helpdesk and Woodpecker.co - APIANT.ai"
description: "When \"New Ticket\" fires in Jitbit Helpdesk, your agent runs \"Find Prospect Email\" in Woodpecker.co."
canonical: "https://apiant.ai/connect/jitbit-helpdesk-to-woodpecker-co"
---

# Connect Jitbit Helpdesk and Woodpecker.co

When **New Ticket** fires in [Jitbit Helpdesk](https://apiant.ai/connections/jitbit-helpdesk), your agent runs **Find Prospect Email** in [Woodpecker.co](https://apiant.ai/connections/woodpecker-co), or **Campaign Completed** in Woodpecker.co to **Add tag to ticket** in Jitbit Helpdesk. Describe the whole flow and it is built, tested on every scenario and kept running.

Jitbit Helpdesk **1** trigger Jitbit Helpdesk **19** actions Woodpecker.co **20** triggers Woodpecker.co **5** actions

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

## What do you want Jitbit Helpdesk and Woodpecker.co 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 Jitbit Helpdesk and Woodpecker.co can do together

### From Jitbit Helpdesk to Woodpecker.co

- When **New Ticket** in Jitbit Helpdesk then **Find Prospect Email** in Woodpecker.co
- When **New Ticket** in Jitbit Helpdesk then **Create/Update Prospect** in Woodpecker.co

### From Woodpecker.co to Jitbit Helpdesk

- When **Campaign Completed** in Woodpecker.co then **Add tag to ticket** in Jitbit Helpdesk
- When **Manual Task Created** in Woodpecker.co then **Create Ticket** in Jitbit Helpdesk

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

## Triggers and actions 21 triggers · 24 actions

- 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.

- Trigger

**Campaign Completed**

Triggers when a Woodpecker campaign status changes to COMPLETED.

- Trigger

**Email Opened**

Triggers when a prospect opens your email.

- Trigger

**Email Sent**

Triggers when Woodpecker sends an email to prospect from campaign.

- Trigger

**Follow-Up After Autoreply**

Triggers when you set a date for resuming follow-ups after you got an autoreply from a prospect.

- Trigger

**Link Clicked**

Triggers when a prospect clicks on a link in your email.

- Trigger

**Manual Task Created**

Triggers when a manual task of any type is created.

- Trigger

**Manual Task Done**

Triggers when a manual task is marked as done.

- Trigger

**Manual Task Ignored**

Triggers when a manual task is marked as ignored.

- Trigger

**Prospect Autoreplied**

Triggers when you get an autoresponder from a prospect, or when you manually mark a prospect as AUTOREPLIED.

- Trigger

**Prospect Blacklisted**

Triggers when a prospect status is changed to BLACKLISTED manually or when prospect unsubscribes from Woodpecker.

- Trigger

**Prospect Bounced**

Triggers when a prospect’s email address bounces your message and the prospect status gets changed to BOUNCED in Woodpecker.

- Trigger

**Prospect Interested**

Triggers when a prospect is marked as INTERESTED.

- Trigger

**Prospect Invalid**

Triggers when a prospect’s email address doesn't exist on an external server. This check happens when Woodpecker tries to send an email to this prospect. Status is changed to INVALID in Woodpecker.

- Trigger

**Prospect Maybe Later**

Triggers when a prospect's interest level is marked as MAYBE LATER.

- Trigger

**Prospect Nonresponsive**

Triggers when a prospect's status is changed to NONRESPONSIVE

- Trigger

**Prospect Not Interested**

Triggers when a prospect is marked as NOT INTERESTED.

- Trigger

**Prospect Opt Out**

Triggers when prospect unsubscribes from your emails or is marked as OPT-OUT manually.

- Trigger

**Prospect Replied**

Triggers when a prospect replies to your email or is manually marked as REPLIED in Woodpecker.

- Trigger

**Prospect Saved**

Triggers when a Woodpecker prospect is created or updated.

- Trigger

**Secondary Reply**

Triggers when a secondary reply is found by Woodpecker.

- Action

**Blacklist Domain**

Add a domain to a blacklist. It will automatically block ongoing and future sending to all prospects within a given domain.

- Action

**Create/Update Prospect**

Adds a new prospect or Updates existing prospect in the list of Prospects.

- Action

**Create/Update Prospect in Campaign**

Adds a new prospect or updates existing prospect's data in a campaign of choice.

- Action

**Find Prospect Email**

Finds prospect by email address.

- Action

**Stop Follow-Ups**

Stop follow-ups planned for this prospect.

## Each app on its own

- [ **Jitbit Helpdesk** A great help desk app for small and medium sized companies.](https://apiant.ai/connections/jitbit-helpdesk)
- [ **Woodpecker.co** Woodpecker.co helps B2B companies directly contact prospective clients by automated sending of personalized...](https://apiant.ai/connections/woodpecker-co)

Reviews

## What our customers say

## More from Jitbit Helpdesk

- [ **Jitbit Helpdesk to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/jitbit-helpdesk-to-salesforce)
- [ **Jitbit Helpdesk to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/jitbit-helpdesk-to-slack)
- [ **Jitbit Helpdesk to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/jitbit-helpdesk-to-mailchimp)
- [ **Jitbit Helpdesk to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/jitbit-helpdesk-to-stripe)
- [ **Jitbit Helpdesk to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/jitbit-helpdesk-to-shopify)
- [ **Jitbit Helpdesk to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/jitbit-helpdesk-to-quickbooks-online)

## More into Woodpecker.co

- [ **HubSpot to Woodpecker.co** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-woodpecker-co)
- [ **Salesforce to Woodpecker.co** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-woodpecker-co)
- [ **Slack to Woodpecker.co** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-woodpecker-co)
- [ **Google Sheets to Woodpecker.co** Google Sheets](https://apiant.ai/connect/google-sheets-to-woodpecker-co)
- [ **Gmail to Woodpecker.co** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-woodpecker-co)
- [ **Google Calendar to Woodpecker.co** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-woodpecker-co)

Questions

## Jitbit Helpdesk and Woodpecker.co, answered

###

### What can start an automation from Jitbit Helpdesk?

Any of Jitbit Helpdesk's 1 trigger in the catalog, including New Ticket. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Woodpecker.co when something happens in Jitbit Helpdesk?

Any of Woodpecker.co's 5 actions, including Create/Update Prospect, Create/Update Prospect in Campaign, Blacklist Domain and Find Prospect Email. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Woodpecker.co to Jitbit Helpdesk?

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

###

### Do I have to build a connector for Jitbit Helpdesk or Woodpecker.co?

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