Integration
Connect Woodpecker.co to Neon Postgres
When something happens in Woodpecker.co, your agent does the next thing in Neon Postgres. 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 Neon Postgres 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 Neon Postgres
When Campaign Completed in Woodpecker.co
then Add branch in Neon Postgres
When Manual Task Created in Woodpecker.co
then Add compute endpoint in Neon Postgres
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 Neon Postgres
Triggers and actions 20 triggers · 34 actions
Trigger
Campaign CompletedTriggers when a Woodpecker campaign status changes to COMPLETED.
Trigger
Email OpenedTriggers when a prospect opens your email.
Trigger
Email SentTriggers when Woodpecker sends an email to prospect from campaign.
Trigger
Follow-Up After AutoreplyTriggers when you set a date for resuming follow-ups after you got an autoreply from a prospect.
Trigger
Link ClickedTriggers when a prospect clicks on a link in your email.
Trigger
Manual Task CreatedTriggers when a manual task of any type is created.
Trigger
Manual Task DoneTriggers when a manual task is marked as done.
Trigger
Manual Task IgnoredTriggers when a manual task is marked as ignored.
Trigger
Prospect AutorepliedTriggers when you get an autoresponder from a prospect, or when you manually mark a prospect as AUTOREPLIED.
Trigger
Prospect BlacklistedTriggers when a prospect status is changed to BLACKLISTED manually or when prospect unsubscribes from Woodpecker.
Trigger
Prospect BouncedTriggers when a prospect’s email address bounces your message and the prospect status gets changed to BOUNCED in Woodpecker.
Trigger
Prospect InterestedTriggers when a prospect is marked as INTERESTED.
Trigger
Prospect InvalidTriggers 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 LaterTriggers when a prospect's interest level is marked as MAYBE LATER.
Trigger
Prospect NonresponsiveTriggers when a prospect's status is changed to NONRESPONSIVE
Trigger
Prospect Not InterestedTriggers when a prospect is marked as NOT INTERESTED.
Trigger
Prospect Opt OutTriggers when prospect unsubscribes from your emails or is marked as OPT-OUT manually.
Trigger
Prospect RepliedTriggers when a prospect replies to your email or is manually marked as REPLIED in Woodpecker.
Trigger
Prospect SavedTriggers when a Woodpecker prospect is created or updated.
Trigger
Secondary ReplyTriggers when a secondary reply is found by Woodpecker.
Action
Blacklist DomainAdd a domain to a blacklist. It will automatically block ongoing and future sending to all prospects within a given domain.
Action
Create/Update ProspectAdds a new prospect or Updates existing prospect in the list of Prospects.
Action
Create/Update Prospect in CampaignAdds a new prospect or updates existing prospect's data in a campaign of choice.
Action
Find Prospect EmailFinds prospect by email address.
Action
Stop Follow-UpsStop follow-ups planned for this prospect.
Action
Add branchCreate a new branch in a Neon project.
Action
Add compute endpointCreates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.
Action
Add databaseCreates a new Postgres database in a Neon project branch, owned by an existing role.
Action
Add projectCreates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.
Action
Add roleCreates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.
Action
Delete branchDelete a branch by project_id and branch_id.
Action
Delete compute endpointDeletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.
Action
Delete databaseDeletes the specified database from a branch of a Neon project.
Action
Delete projectDeletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.
Action
Delete roleDeletes the specified Postgres role from a Neon branch.
Action
Get branchRetrieves details of a branch in a Neon project.
Action
Get compute endpointRetrieve details about a compute endpoint.
Action
Get connection URIRetrieve a Postgres connection URI for a database/role/branch/endpoint combination.
Action
Get databaseRetrieves details of a database on a Neon project branch.
Action
Get projectRetrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.
Action
Get roleRetrieves details about a Postgres role (user) on a Neon branch.
Action
Get role passwordRetrieves the password for a Postgres role on a Neon branch.
Action
List branchesRetrieve a list of branches for a Neon project.
Action
List compute endpointsLists the compute endpoints (Neon compute instances) in a project.
Action
List databasesLists the databases on a branch of a Neon project.
Action
List operationsLists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.
Action
List projectsLists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.
Action
List rolesLists the Postgres roles on a Neon project branch.
Action
Start compute endpointStart (resume) a suspended compute endpoint.
Action
Suspend compute endpointSuspends the specified Neon compute endpoint (scales it to zero).
Action
Update branchUpdate a branch's properties (e.g. name, protected) by project_id and branch_id.
Action
Update compute endpointUpdates an existing compute endpoint in a Neon project by ID.
Action
Update databaseUpdates the name or owner of a database on a Neon project branch.
Action
Update projectUpdate settings for a Neon project by project_id.
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 Neon Postgres
HubSpot to Neon PostgresHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Neon PostgresSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Neon PostgresSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Neon PostgresGoogle Sheets
Gmail to Neon PostgresGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Neon PostgresGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Woodpecker.co and Neon Postgres, 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 Neon Postgres when something happens in Woodpecker.co?
Any of Neon Postgres's 29 actions, including Update branch, Update compute endpoint, Update database and Update project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Postgres to Woodpecker.co?
Neon Postgres has no triggers in the catalog today, so automations start in Woodpecker.co. If you need the other direction, ask: your agent reads Neon Postgres's API documentation and adds it.
Do I have to build a connector for Woodpecker.co or Neon Postgres?
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.