Integration
Connect Woodpecker.co to Qase
When something happens in Woodpecker.co, your agent does the next thing in Qase. Describe it 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 Woodpecker.co and Qase 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 Woodpecker.co can start in Qase
When Campaign Completed in Woodpecker.co
then Add defect in Qase
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 Qase
Triggers and actions 20 triggers · 32 actions
- Campaign Completed
Triggers when a Woodpecker campaign status changes to COMPLETED.
- Email Opened
Triggers when a prospect opens your email.
- Email Sent
Triggers when Woodpecker sends an email to prospect from campaign.
- Follow-Up After Autoreply
Triggers when you set a date for resuming follow-ups after you got an autoreply from a prospect.
- Link Clicked
Triggers when a prospect clicks on a link in your email.
- Manual Task Created
Triggers when a manual task of any type is created.
- Manual Task Done
Triggers when a manual task is marked as done.
- Manual Task Ignored
Triggers when a manual task is marked as ignored.
- Prospect Autoreplied
Triggers when you get an autoresponder from a prospect, or when you manually mark a prospect as AUTOREPLIED.
- Prospect Blacklisted
Triggers when a prospect status is changed to BLACKLISTED manually or when prospect unsubscribes from Woodpecker.
- Prospect Bounced
Triggers when a prospect’s email address bounces your message and the prospect status gets changed to BOUNCED in Woodpecker.
- Prospect Interested
Triggers when a prospect is marked as INTERESTED.
- 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.
- Prospect Maybe Later
Triggers when a prospect's interest level is marked as MAYBE LATER.
- Prospect Nonresponsive
Triggers when a prospect's status is changed to NONRESPONSIVE
- Prospect Not Interested
Triggers when a prospect is marked as NOT INTERESTED.
- Prospect Opt Out
Triggers when prospect unsubscribes from your emails or is marked as OPT-OUT manually.
- Prospect Replied
Triggers when a prospect replies to your email or is manually marked as REPLIED in Woodpecker.
- Prospect Saved
Triggers when a Woodpecker prospect is created or updated.
- Secondary Reply
Triggers when a secondary reply is found by Woodpecker.
- Blacklist Domain
Add a domain to a blacklist. It will automatically block ongoing and future sending to all prospects within a given domain.
- Create/Update Prospect
Adds a new prospect or Updates existing prospect in the list of Prospects.
- Create/Update Prospect in Campaign
Adds a new prospect or updates existing prospect's data in a campaign of choice.
- Find Prospect Email
Finds prospect by email address.
- Stop Follow-Ups
Stop follow-ups planned for this prospect.
- Add defect
Adds a new defect to a Qase project.
- Add milestone
Creates a milestone in a Qase project.
- Add project
Create a new project.
- Add run
Create a new test run in a project.
- Add test case
Create a new test case in a project.
- Add test run result
Create a result for a test run.
- Complete run
Mark a specific test run as completed.
- Delete project
Delete a project by code.
- Delete run
Delete a test run by id.
- Delete test case
Delete a test case by id.
- Find entities by QQL
Searches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.
- Get defect
Get a specific defect by id.
- Get project
Get a project by its code.
- Get run
Retrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.
- Get test case
Get a specific test case by id.
- Get test run result
Get a test run result by hash code.
- List defects
Returns all defects in a Qase project, optionally filtered by status.
- List milestones
Get all milestones in a project.
- List projects
Lists every project available to the connected Qase account.
- List runs
Get all test runs in a project.
- List test cases
Get all test cases in a project.
- List test run results
Get all results for a project's test runs.
- Resolve defect
Marks a specific defect in a Qase project as resolved.
- Update defect
Update an existing defect.
- Update run
Update a specific test run.
- Update test case
Updates an existing test case in a Qase project. Only the fields you fill in are changed.
- Update test run result
Update a test run result.
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 Woodpecker.co
Woodpecker.co to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Woodpecker.co to MailchimpMailchimp marketing automation and email platform.
Woodpecker.co to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Woodpecker.co to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Woodpecker.co to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Woodpecker.co to YouTubeYouTube is a video-sharing platform with user-generated content, live streaming, and monetization...
More into Qase
HubSpot to QaseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to QaseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to QaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to QaseGoogle Sheets
Gmail to QaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Woodpecker.co and Qase, 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 Qase when something happens in Woodpecker.co?
Any of Qase's 27 actions, including Update defect, Update run, Update test case and Update test run result. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qase to Woodpecker.co?
Qase has no triggers in the catalog today, so automations start in Woodpecker.co. If you need the other direction, ask: your agent reads Qase's API documentation and adds it.
Do I have to build a connector for Woodpecker.co or Qase?
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.