Actions22
- Collection Actions
- Dataset Actions
- Dataset Search Actions
- Installation Actions
- Institution Actions
- Occurrence Actions
- Occurrence Count Actions
- Occurrence Search Actions
- Occurrence Search Catalog Number Actions
- Occurrence Search Collection Code Actions
- Occurrence Search Occurrence ID Actions
- Occurrence Search Recorded By Actions
- Occurrence Search Record Number Actions
- Occurrence Search Institution Code Actions
- Organization Actions
- Name Parser Actions
- Network Actions
- Node Actions
- Species Actions
- Species Match Actions
- Species Search Actions
- Species Suggest Actions
Collection → Get
AI-generatedOverview
This node integrates with the GBIF (Global Biodiversity Information Facility) API to retrieve biodiversity data. Specifically, for the Collection - Get operation, it fetches detailed information about a particular collection or its related sub-resources from the GBIF database.
Common scenarios where this node is beneficial include:
- Retrieving metadata about a specific biological collection by its ID.
- Accessing related sub-resources such as comments, contacts, identifiers, tags, and other metadata linked to a collection.
- Integrating biodiversity collection data into workflows for research, data analysis, or reporting.
Practical example:
- A researcher wants to get detailed information about a collection of specimens stored in a natural history museum. By providing the collection ID, the node fetches all relevant data including contact persons and tags associated with that collection.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the collection to retrieve. |
| Sub-Resource | Optional related resource of the collection to fetch. Options: (empty), Comment, Contact, Contact Person, Identifier, Machine Tag, Master Source Metadata, Occurrence Mapping, Tag |
Output
The node outputs an array of JSON objects representing the requested collection data or its sub-resource data retrieved from the GBIF API.
- The
jsonoutput contains the full response from the GBIF API endpoint/grscicoll/collection/{id}/{subResource}. - The structure depends on the selected sub-resource; if no sub-resource is specified, it returns the main collection details.
- No binary data output is produced by this node.
Dependencies
- This node requires internet access to call the public GBIF API at
https://api.gbif.org/v1. - No authentication or API keys are required since the GBIF API is publicly accessible.
- No additional n8n credentials or environment variables are needed.
Troubleshooting
- Empty or invalid ID: If the collection ID is not provided or incorrect, the API will return an error or empty result. Ensure the ID is valid and correctly entered.
- Invalid sub-resource: Selecting a sub-resource that does not exist for the given collection may result in an error or empty response.
- Network issues: Since the node relies on external API calls, network connectivity problems can cause request failures.
- API rate limits: Although GBIF API is public, excessive requests might be throttled. Consider adding delays or handling retries.
Common error messages:
- HTTP 404 Not Found: The collection ID or sub-resource does not exist.
- HTTP 400 Bad Request: Invalid parameters supplied.
- Network timeout or connection errors: Check internet connectivity.
Links and References
- GBIF API Documentation: https://www.gbif.org/developer/summary
- GBIF Collections API: https://www.gbif.org/developer/occurrence#collections
- GBIF Homepage: https://www.gbif.org