Actions11
Overview
This node manages WhatsApp session connections and configurations, specifically focusing on configuring S3 storage settings in the "Configure S3" operation. It allows users to set up and manage Amazon S3 (or compatible) storage for media files related to WhatsApp sessions. This is useful for scenarios where media files need to be stored externally for scalability, backup, or sharing purposes.
Practical examples include:
- Storing WhatsApp media files such as images, videos, and audio messages in an S3 bucket.
- Configuring how media is delivered in webhook events (e.g., as Base64 data, via S3 URLs, or both).
- Setting retention policies to automatically delete files after a certain number of days.
- Using custom endpoints and public URLs for accessing stored media, which is helpful when using S3-compatible services or CDNs.
Properties
| Name | Meaning |
|---|---|
| Access Key | The access key credential for authenticating with the S3 service. |
| Bucket | The name of the S3 bucket where media files will be stored. |
| Enable S3 | Boolean flag to enable or disable S3 storage functionality. |
| Endpoint | The URL endpoint of the S3 service (default is https://s3.amazonaws.com). |
| Media Delivery | How media should be delivered in webhook events: "Base64 Only", "S3 Only", or "Both Base64 and S3". |
| Path Style | Whether to use path-style URLs instead of virtual-hosted style URLs for S3 objects. |
| Public URL | A public URL prefix used to access files, useful for CDN or proxy setups. |
| Region | The AWS region or equivalent for the S3 bucket (default is "us-east-1"). |
| Retention Days | Number of days to retain files before they are deleted from storage. |
| Secret Key | The secret key credential paired with the access key for S3 authentication. |
Output
The node outputs JSON data representing the response from the API call that configures the S3 settings. This typically includes confirmation of the configuration status or details about the applied settings.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the WhatsApp session management API.
- Needs valid credentials for the WhatsApp API (an API key or token).
- Requires valid S3 credentials (access key and secret key) for configuring storage.
- The node expects the S3 service to be accessible at the specified endpoint.
- No additional environment variables are explicitly required beyond standard n8n credential setup.
Troubleshooting
- Invalid Credentials: If the access key or secret key is incorrect, the configuration will fail. Verify keys and permissions on the S3 side.
- Bucket Not Found or Access Denied: Ensure the specified bucket exists and the credentials have proper permissions.
- Incorrect Endpoint or Region: Using wrong endpoint URLs or regions can cause connectivity issues. Confirm these values match your S3 provider's requirements.
- Retention Policy Issues: Setting retention days to invalid values may cause errors; use positive integers.
- Media Delivery Misconfiguration: Choosing incompatible media delivery options might lead to unexpected behavior in webhook events.
- Network Issues: Connectivity problems between n8n and the S3 endpoint or WhatsApp API can cause timeouts or failures.
Common error messages usually relate to authentication failures, permission denials, or network timeouts. Resolving them involves checking credentials, bucket existence, network accessibility, and correct parameter usage.
Links and References
- Amazon S3 Documentation
- AWS S3 REST API Reference
- n8n Documentation on Credential Management
- WhatsApp Business API Overview (for context on WhatsApp session management)