---
title: "Connect Woodpecker.co to Luma - APIANT.ai"
description: "When \"Campaign Completed\" fires in Woodpecker.co, your agent runs \"Add ticket type\" in Luma."
canonical: "https://apiant.ai/connect/woodpecker-co-to-luma"
---

# Connect Woodpecker.co to Luma

When **Campaign Completed** fires in [Woodpecker.co](https://apiant.ai/connections/woodpecker-co), your agent runs **Add ticket type** in [Luma](https://apiant.ai/connections/luma). Describe the whole flow and it is built, tested on every scenario and kept running.

Woodpecker.co **20** triggers Woodpecker.co **5** actions Luma **17** actions

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

## What do you want Woodpecker.co and Luma 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 Woodpecker.co can start in Luma

- When **Campaign Completed** in Woodpecker.co then **Add ticket type** in Luma
- When **Manual Task Created** in Woodpecker.co then **Apply contact tag** in Luma

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

## Triggers and actions 20 triggers · 22 actions

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

- Action

**Add guests**

Adds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.

- Action

**Add host**

Adds a host to a Luma event, as a manager or as check-in staff, by email address.

- Action

**Add ticket type**

Creates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.

- Action

**Apply contact tag**

Applies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.

- Action

**Block contact**

Blocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.

- Action

**Cancel event**

Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.

- Action

**Create Calendar Person**

Adds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.

- Action

**Get calendar**

Returns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.

- Action

**Get event**

Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.

- Action

**Get guest**

Returns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.

- Action

**Import contacts**

Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.

- Action

**List contacts**

Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.

- Action

**List events**

Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.

- Action

**List guests**

Returns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.

- Action

**List ticket types**

Returns every ticket type set up for a Luma event, including its name, price and capacity.

- Action

**Send invites**

Sends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.

- Action

**Update guest status**

Changes a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.

## Each app on its own

- [ **Woodpecker.co** Woodpecker.co helps B2B companies directly contact prospective clients by automated sending of personalized...](https://apiant.ai/connections/woodpecker-co)
- [ **Luma** Luma is an event management app that gives you the tools to host delightful events.](https://apiant.ai/connections/luma)

Reviews

## What our customers say

## More from Woodpecker.co

- [ **Woodpecker.co to Google Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/woodpecker-co-to-google-drive)
- [ **Woodpecker.co to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/woodpecker-co-to-mailchimp)
- [ **Woodpecker.co to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/woodpecker-co-to-jira)
- [ **Woodpecker.co to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/woodpecker-co-to-linkedin)
- [ **Woodpecker.co to Facebook** Facebook is a social media and advertising platform used by individuals and businesses to connect, share...](https://apiant.ai/connect/woodpecker-co-to-facebook)
- [ **Woodpecker.co to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/woodpecker-co-to-anthropic)

## More into Luma

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

Questions

## Woodpecker.co and Luma, answered

###

### What can start an automation from Woodpecker.co?

Any of Woodpecker.co's 20 triggers in the catalog, including Campaign Completed, Manual Task Created, Email Opened and Email Sent. Describe the moment in plain language and your agent picks the right one.

###

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

Any of Luma's 17 actions, including Create Calendar Person, Send invites, Update guest status and Add guests. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Luma to Woodpecker.co?

Luma has no triggers in the catalog today, so automations start in Woodpecker.co. If you need the other direction, ask: your agent reads Luma's API documentation and adds it.

###

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

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