PNTA icon

PNTA

Send push notifications and manage devices using PNTA.io
Join our community

Actions4

Overview

This node integrates with the PNTA.io service to list topics used for push notifications. It allows users to retrieve a paginated list of topics that can be targeted for sending notifications or managing subscriptions. This is useful in scenarios where you want to display available notification topics, manage topic subscriptions, or automate workflows based on topic data.

For example, you might use this node to:

  • Fetch all available notification topics to present them in a user interface.
  • Automate sending notifications to specific topics by first retrieving their identifiers.
  • Monitor and audit topics configured in your PNTA.io account.

Properties

Name Meaning
Additional Fields Collection of optional parameters to customize the listing:
- Limit Maximum number of results to return (minimum 1). Defaults to 50.
- Page Page number for pagination, starting from 1. Defaults to 1.

Output

The node outputs a JSON array containing topic objects retrieved from the PNTA.io API. Each object represents a topic with its associated properties as defined by the PNTA.io service. The exact structure depends on the API response but typically includes identifiers, names, and metadata related to each topic.

No binary data output is produced by this operation.

Dependencies

  • Requires an active PNTA.io account.
  • Needs an API authentication token credential configured in n8n to authorize requests to the PNTA.io API.
  • The node makes HTTP requests to https://app.pnta.io endpoint.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Pagination issues: If no results are returned, verify that the Page and Limit parameters are within valid ranges and that topics exist.
  • Network errors: Check network connectivity and that the PNTA.io service is reachable.
  • Unexpected API responses: Confirm that the PNTA.io API has not changed and that the node version is compatible.

Links and References

Discussion