Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
The "Meeting Links" resource with the "Get Meeting Links" operation allows users to retrieve meeting links associated with a specified WhatsApp number. This node is useful for scenarios where you want to programmatically access and filter meeting links created or managed via the Wassenger WhatsApp API, such as voice or video call links.
Practical examples include:
- Fetching all active video meeting links created after a certain date.
- Searching meeting links by URL or token.
- Paginating through meeting links results to display in a dashboard or report.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number from which to retrieve meeting links. |
| Filters | A collection of optional filters to narrow down the search results: |
| - Search | Search meeting links by URL, token, or message content. |
| - Created Before | Filter links created before a specific date/time. |
| - Created After | Filter links created after a specific date/time. |
| - Expires Before | Filter links that expire before a specific date/time. |
| - Expires After | Filter links that expire after a specific date/time. |
| - Link Type | Filter links by type; options are Voice or Video. |
| - Results Page Size | Number of results to return per page (default 20). |
| - Page Number | Page number for paginated results, starting from 0. |
Output
The node outputs an array of JSON objects representing meeting links matching the specified criteria. Each object typically contains details about a meeting link such as its URL, token, message, creation and expiration timestamps, and type (voice or video).
If binary data were involved (e.g., files), it would be summarized here, but this node focuses on JSON data related to meeting links.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger API service to fetch meeting link data.
- No additional environment variables or external services are explicitly required beyond the API key.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp number ID will result in no data or errors.
- Incorrect API key or authentication failure will cause authorization errors.
- Using invalid date formats in filters may lead to request failures.
- Requesting pages beyond available results will return empty arrays.
Error messages:
- Authentication errors: Check that the API key credential is correctly configured.
- Validation errors on filters: Ensure date/time values are valid ISO strings.
- Network or API downtime: Retry later or check network connectivity.
Links and References
- Wassenger API Documentation (general reference for API endpoints)
- n8n documentation on creating custom nodes