Wapisimo Webhook icon

Wapisimo Webhook

Manage Wapisimo Webhooks
Join our community

Actions3

Overview

The Wapisimo Webhook node for n8n allows you to manage webhooks associated with a specific phone in the Wapisimo platform. The "List Webhooks" operation retrieves all webhooks currently configured for a given phone, making it useful for monitoring, auditing, or managing webhook integrations. Typical use cases include:

  • Auditing which endpoints are set up to receive notifications from a particular phone.
  • Automating the process of listing and reviewing webhook configurations as part of workflow management.
  • Integrating with other systems that need to know about existing webhook subscriptions.

Practical Example

Suppose you have several phones managed via Wapisimo and want to periodically check which webhooks are active for each device. You can use this node in an n8n workflow to fetch and log all webhooks for a specified phone ID.

Properties

Name Type Meaning
Phone ID String The unique identifier of the phone whose webhooks you want to list.

Output

The node outputs a JSON array where each item represents the response from the Wapisimo API for the "List Webhooks" operation. The structure of each json output field corresponds directly to the API's response for listing webhooks. Typically, this includes details such as:

{
  "webhooks": [
    {
      "id": "string",
      "url": "string",
      "createdAt": "string",
      // ...other fields as provided by the API
    }
  ]
}

Note: The exact fields depend on the Wapisimo API's response schema.

Dependencies

  • External Service: Requires access to the Wapisimo API.
  • API Key: You must provide valid Wapisimo API credentials (API key) via the wapiSimoApi credential in n8n.
  • n8n Configuration: Ensure the credential is set up in your n8n instance.

Troubleshooting

  • Invalid API Key / Unauthorized:
    If the API key is missing or incorrect, the node will throw an authentication error. Make sure your wapiSimoApi credential is correctly configured.
  • Phone ID Not Found:
    If the provided Phone ID does not exist, the API may return a "not found" error. Double-check the Phone ID value.
  • Network Issues:
    Errors related to network connectivity or timeouts may occur if the Wapisimo API is unreachable.
  • Error Handling:
    If "Continue On Fail" is enabled, errors for individual items will be returned in the output under an error property. Otherwise, the workflow will stop on the first error.

Links and References

Discussion