Overview
This node manages WhatsApp sessions using the Wuzapi service, focusing on configuring S3 storage settings for media files. The "Configure S3" operation allows users to enable or disable S3 storage and set detailed configuration parameters such as endpoint URL, region, bucket name, access keys, and delivery preferences. This is useful for scenarios where WhatsApp media needs to be stored externally in an S3-compatible storage system (e.g., AWS S3, MinIO) for scalability, backup, or CDN integration.
Practical examples include:
- Automatically uploading WhatsApp media files to a dedicated S3 bucket for archival.
- Delivering media either as base64 data, via S3 URLs, or both, depending on downstream processing needs.
- Setting retention policies to automatically expire stored media after a certain number of days.
Properties
| Name | Meaning |
|---|---|
| S3 Enabled | Whether S3 storage is enabled (true/false). |
| S3 Configuration | Collection of S3 connection and behavior settings: |
| - Endpoint | S3 endpoint URL, e.g., https://s3.amazonaws.com (default for AWS S3). |
| - Region | S3 region, e.g., us-east-1. |
| - Bucket | Name of the S3 bucket to use for storing media files. |
| - Access Key | S3 access key ID for authentication. |
| - Secret Key | S3 secret access key (password type, hidden). |
| - Path Style | Whether to use path-style URLs (required for some services like MinIO). |
| - Public URL | Optional custom public URL for accessing files (e.g., a CDN URL). |
| - Media Delivery | How to deliver media files: options are "Base64 Only", "S3 URL Only", or "Both". |
| - Retention Days | Number of days to retain files before expiration; 0 means no expiration (range 0–365). |
Output
The node outputs JSON data reflecting the result of the S3 configuration request. This typically includes confirmation of the updated settings or status information from the Wuzapi API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Wuzapi API service with appropriate API credentials.
- Needs valid S3 credentials and access to the specified S3-compatible storage.
- The node uses an internal helper function to make authenticated HTTP requests to the Wuzapi backend.
Troubleshooting
- Invalid Credentials: If the access key or secret key is incorrect, the API will reject the configuration. Verify credentials and permissions on the S3 provider.
- Incorrect Endpoint or Region: Using wrong endpoint URLs or regions can cause connection failures. Ensure these match your S3 provider's specifications.
- Bucket Access Issues: The configured bucket must exist and be accessible with the provided credentials.
- Path Style URL Misconfiguration: For MinIO or other S3-compatible services requiring path-style URLs, ensure the "Path Style" option is enabled.
- Retention Days Limits: Values outside the allowed range (0–365) may cause errors; keep within limits.
- API Errors: Network issues or invalid parameters will result in error messages from the Wuzapi API. Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- AWS S3 Documentation
- MinIO Path Style Access
- Wuzapi Official Documentation (replace with actual URL if available)