Overview
This node manages WhatsApp sessions using the Wuzapi service, providing various operations to control and configure the session. The "Configure S3" operation specifically allows users to enable or disable S3-compatible storage for media files related to the WhatsApp session. It supports configuring connection details such as endpoint, region, bucket, access keys, and options for media delivery and retention.
Common scenarios where this node is beneficial include:
- Automating WhatsApp session management in workflows.
- Configuring cloud storage (S3 or compatible services) to store WhatsApp media files securely.
- Customizing how media files are delivered (as base64 data, URLs, or both).
- Managing retention policies for stored media.
Practical example:
- A user wants to store all WhatsApp media files in a private S3 bucket with a custom public URL and retain files for 60 days. They can use this node's "Configure S3" operation to set up these parameters programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| S3 Enabled | Boolean flag to enable or disable S3 storage integration. |
| S3 Configuration | Collection of settings required when S3 storage is enabled: - Endpoint: URL of the S3 service endpoint (default is AWS S3). - Region: AWS region or equivalent. - Bucket: Name of the S3 bucket. - Access Key: Access key ID for authentication. - Secret Key: Secret access key for authentication. - Path Style: Whether to use path-style URLs (needed for some services like MinIO). - Public URL: Optional custom public URL for accessing stored files. - Media Delivery: How media files are delivered; options are Base64 only, S3 URL only, or both. - Retention Days: Number of days to keep files before expiration (0 means no expiration). |
Output
The node outputs JSON data reflecting the result of the "Configure S3" operation. This typically includes confirmation of the configuration status or error messages if the operation fails.
No binary data output is associated with this operation.
Dependencies
- Requires an active connection to the Wuzapi API service.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- For S3 configuration, valid S3-compatible storage credentials and bucket access are necessary.
- Network access to the specified S3 endpoint must be available from the environment running n8n.
Troubleshooting
- Invalid Credentials or Access Denied: If the provided access key or secret key is incorrect or lacks permissions, the node will fail to configure S3. Verify credentials and bucket policies.
- Incorrect Endpoint or Region: Using wrong endpoint URLs or regions may cause connection failures. Ensure these match your S3 provider's specifications.
- Path Style URL Issues: Some S3-compatible services require path-style URLs. If media files are not accessible, try toggling the "Path Style" option.
- Retention Days Limits: Setting retention days outside the allowed range (0-365) might cause errors. Use values within this range.
- Network Connectivity: Ensure that the n8n instance can reach both the Wuzapi API and the S3 endpoint without firewall restrictions.
- Error Messages: Errors returned by the Wuzapi API will be included in the node output. Review these messages for specific issues.
Links and References
- Amazon S3 Documentation
- MinIO Path Style Access
- Wuzapi Official Site (for API documentation and support)