Wappfy

Overview

This node interacts with WhatsApp through the Wappfy API, specifically enabling operations on various WhatsApp resources. For the Channel resource with the List operation, it retrieves a list of WhatsApp channels accessible to the user. This can be filtered by the user's role in those channels (e.g., Owner, Admin, Subscriber).

Common scenarios where this node is beneficial include:

• Managing and monitoring WhatsApp channels programmatically.
• Retrieving channel lists for analytics or reporting.
• Filtering channels based on user roles to perform role-specific actions.

Practical example:

• A marketing automation workflow that fetches all channels where the user is an admin to send targeted announcements.
• An integration that lists all subscribed channels to display them in a dashboard.

Properties

Output

The output is an array of JSON objects representing the channels retrieved from the Wappfy API. Each item corresponds to one channel's data as returned by the API. The exact structure depends on the API response but typically includes channel identifiers, names, descriptions, roles, and other metadata.

No binary data output is produced by this operation.

Example output snippet (conceptual):

[
  {
    "id": "channel123",
    "name": "Marketing Channel",
    "description": "Channel for marketing updates",
    "role": "ADMIN",
    ...
  },
  {
    "id": "channel456",
    "name": "Support Channel",
    "description": "Customer support discussions",
    "role": "SUBSCRIBER",
    ...
  }
]

Dependencies

• Requires a valid Wappfy API credential with an API key and instance name configured in n8n.
• The node makes HTTP requests to the Wappfy API base URL using these credentials.
• No additional external dependencies are required.

Troubleshooting

• Common issues:

  • Invalid or missing API key or instance name will cause authentication failures.
  • Network connectivity problems may prevent reaching the Wappfy API.
  • Using an unsupported or incorrect role filter value might result in empty results.

• Error messages:

  • Authentication errors usually indicate invalid credentials; verify API key and instance name.
  • HTTP 4xx or 5xx errors suggest issues with the request or server; check parameters and API status.
  • If the node returns an error object in the output, inspect the message for details.

• Resolution tips:

  • Ensure credentials are correctly set up in n8n.
  • Confirm the API endpoint is reachable from your environment.
  • Use the "All" role option to test if filtering causes empty results.

Links and References

• Wappfy API Documentation (for detailed API endpoints and data structures)
• n8n Documentation (for general node usage and credential setup)