--- title: "Connect Woodpecker.co to SigningHub - APIANT.ai" description: "When \"Campaign Completed\" fires in Woodpecker.co, your agent runs \"Add Document\" in SigningHub." canonical: "https://apiant.ai/connect/woodpecker-co-to-signinghub" --- # Connect Woodpecker.co to SigningHub When **Campaign Completed** fires in [Woodpecker.co](https://apiant.ai/connections/woodpecker-co), your agent runs **Add Document** in [SigningHub](https://apiant.ai/connections/signinghub). Describe the whole flow and it is built, tested on every scenario and kept running. Woodpecker.co **20** triggers Woodpecker.co **5** actions SigningHub **11** 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 SigningHub 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 SigningHub - When **Campaign Completed** in Woodpecker.co then **Add Document** in SigningHub - When **Manual Task Created** in Woodpecker.co then **Add User** in SigningHub 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 SigningHub ## Triggers and actions 20 triggers · 16 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 Digital Signature** Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow. - Action **Add Document** Uploads a document file into an existing SigningHub document package. - Action **Add Electronic Signature** Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow. - Action **Add Recipient to Workflow** Adds a signer or other recipient to a document package's workflow. - Action **Add User** Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details. - Action **Create Integration URL** Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application. - Action **Create Package** Creates a new document package in SigningHub to hold documents and recipients for a signing workflow. - Action **Download Package** Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents. - Action **Get Document Fields** Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields. - Action **Get Package** Returns the details of a SigningHub document package: its name, owner, status and the documents it contains. - Action **Share Document for Signing** Shares a prepared document package with its signers and starts the signing workflow. ## 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) - [ **SigningHub** SigningHub is an e-signature service with a powerful workflow engine that boosts team productivity by...](https://apiant.ai/connections/signinghub) 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 SigningHub - [ **HubSpot to SigningHub** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-signinghub) - [ **Salesforce to SigningHub** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-signinghub) - [ **Slack to SigningHub** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-signinghub) - [ **Google Sheets to SigningHub** Google Sheets](https://apiant.ai/connect/google-sheets-to-signinghub) - [ **Gmail to SigningHub** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-signinghub) - [ **Google Calendar to SigningHub** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-signinghub) Questions ## Woodpecker.co and SigningHub, 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 SigningHub when something happens in Woodpecker.co? Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from SigningHub to Woodpecker.co? SigningHub has no triggers in the catalog today, so automations start in Woodpecker.co. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it. ### ### Do I have to build a connector for Woodpecker.co or SigningHub? 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 SigningHub 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.