EmailConnect icon

EmailConnect

Interact with EmailConnect API for email automation

Actions12

Overview

This node interacts with the EmailConnect API to manage webhooks related to email automation. Specifically, the "Update Webhook" operation allows users to modify an existing webhook's URL and description. This is useful when you need to change where your email data is sent or update metadata about the webhook without recreating it.

Practical examples include:

  • Changing the endpoint URL that receives incoming email notifications.
  • Updating the description to better reflect the webhook’s purpose after changes in your workflow.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook you want to update.
URL The new webhook URL that will receive email data (e.g., https://myapp.com/webhook/email).
Description Optional text describing the webhook, useful for documentation or identification purposes.

Output

The output is a JSON object representing the updated webhook as returned by the EmailConnect API. It typically includes fields such as the webhook ID, URL, description, and possibly other metadata managed by the service.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "url": "string",
  "description": "string"
}

Dependencies

  • Requires an active connection to the EmailConnect API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node uses HTTP methods (PUT) to update webhook details via the /api/webhooks/{webhookId} endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing Webhook ID: Ensure the webhook ID provided exists and is correct.
    • Incorrect URL format: The URL must be a valid HTTPS endpoint capable of receiving webhook payloads.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.

  • Error messages:

    • "Webhook not found": The specified webhook ID does not exist; double-check the ID.
    • "Unauthorized" or "Authentication failed": Check API credentials and permissions.
    • "Invalid URL": The URL parameter does not meet expected format requirements.

Resolving these usually involves verifying input parameters and ensuring proper API credentials are configured.

Links and References

Discussion