Integration
Connect Woodpecker.co to GBIF
When something happens in Woodpecker.co, your agent does the next thing in GBIF. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Woodpecker.co and GBIF to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Woodpecker.co and GBIF
Triggers and actions 20 triggers · 13 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
Find datasetsSearch across all datasets registered with GBIF (occurrence datasets, checklists, etc) by query text, type, publishing org, or country. GET https://api.gbif.org/v1/dataset/search?q=&type=&publishingCountry=&limit=&offset=. Returns a paged list of matching dataset summaries (key, title, type, publishingOrganizationKey).
Action
Find occurrencesSearch occurrence records indexed by GBIF using structured filters (scientific name/taxonKey, country, dataset, date range, geometry, basisOfRecord, etc). GET https://api.gbif.org/v1/occurrence/search?q=&taxonKey=&country=&limit=&offset=. Returns a paged list of matching occurrence records (species observations/specimens with location, date, recordedBy, etc). Max 300 records per page, hard offset+limit cap of 100,000.
Action
Find speciesFull-text search over name usages (species/taxa) in the GBIF Taxonomic Backbone and other checklists. GET https://api.gbif.org/v1/species/search?q={query}&rank=&status=&highertaxon_key=&limit=&offset=. Returns paged list of matching name usages (key, scientificName, rank, kingdom, etc).
Action
Get datasetRetrieve full details of a single GBIF-registered dataset by its key (UUID). GET https://api.gbif.org/v1/dataset/{key}. Returns dataset metadata: title, description, type, license, publishingOrganizationKey, doi, citation, etc.
Action
Get occurrenceRetrieve a single occurrence record by its GBIF occurrence id. GET https://api.gbif.org/v1/occurrence/{gbifId}. Returns the full occurrence record: taxonomy, location (lat/lon/country), event date, recordedBy, dataset, media, etc.
Action
Get speciesRetrieve a single name usage (species/taxon) record by its GBIF usage key. GET https://api.gbif.org/v1/species/{usageKey}. Returns full taxonomic details (scientificName, kingdom, phylum, class, order, family, genus, rank, taxonomicStatus, synonym, etc).
Action
Match species nameFuzzy-match a scientific name string against the GBIF Backbone Taxonomy to resolve it to a canonical taxon key. GET https://api.gbif.org/v2/species/match?name={name}&rank=&kingdom=. Returns the best-matching usageKey/scientificName plus a confidence score and match type (EXACT/FUZZY/HIGHERRANK/NONE) — the standard way to resolve a free-text species name into a stable GBIF key.
Action
Parse scientific nameParse one or more free-text scientific name strings into their structured components (genus, specificEpithet, authorship, rank, etc) using GBIF's name parser. GET https://api.gbif.org/v1/parser/name?name={name} (repeat name= for multiple). Returns a list of ParsedName objects — useful for cleaning/normalizing user-entered species names before other lookups.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.