Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
The "Get Expirations" operation of the Expirations resource retrieves a list of expiration records from an external system. This node is useful for scenarios where you need to monitor or report on various types of expirations such as domain expirations, SSL certificate expirations, warranties, asset fields, or article expirations. For example, it can be used to fetch all upcoming SSL certificate expirations for a company to trigger renewal workflows or to audit asset warranty statuses.
Properties
| Name | Meaning |
|---|---|
| Additional Query Parameters | Optional filters and pagination controls to refine the expirations retrieved. Includes: |
| - Page | The current page number of results to retrieve (number). |
| - Company Id | Filter expirations by a specific company ID (number). |
| - Expiration Type | Filter expirations by type. Possible values: undeclared, domain, ssl_certificate, warranty, asset_field, article_expiration (string). |
| - Resource Id | Filter logs by a specific resource ID; must be used together with Resource Type (number). |
| - Resource Type | Filter logs by resource type (e.g., Asset, AssetPassword, Company, Article); must be used with Resource Id (string). |
| - Page Size | Number of results to return per page (number). |
These parameters allow precise control over which expiration records are fetched and how many are returned per request.
Output
The node outputs JSON data containing the list of expiration records matching the query parameters. Each item in the output typically includes details about the expiration event such as its type, associated resource, expiration date, and related metadata. The exact structure depends on the external API's response schema but generally provides comprehensive information to identify and act upon each expiration.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication with the external service.
- The base URL for API requests is configured via node credentials.
- Relies on the external system's API endpoint that supports querying expirations with filtering and pagination.
Troubleshooting
- Empty Results: If no expirations are returned, verify that the filter parameters (e.g., company_id, expiration_type) are correct and that there are matching records in the external system.
- Invalid Parameter Errors: Ensure that when using
resource_id, the correspondingresource_typeis also provided, as they must be coupled. - Authentication Failures: Confirm that the API key credential is valid and has sufficient permissions to access expiration data.
- Pagination Issues: If too few or too many results are returned, adjust the
pageandpage_sizeparameters accordingly.
Links and References
- Refer to the external API documentation for detailed descriptions of expiration types and resource types.
- Consult n8n documentation on configuring API credentials and handling pagination in nodes.