Actions11
Overview
This node manages WhatsApp session connections and configurations via a DinastiAPI service. Specifically, the "Configure S3" operation allows users to set up Amazon S3 storage settings for media files related to WhatsApp sessions. This is useful for scenarios where media files need to be stored externally in an S3 bucket for scalability, backup, or CDN delivery purposes.
Practical examples include:
- Enabling S3 storage to offload media files from local storage.
- Configuring retention policies to automatically delete old media files.
- Setting up public URLs or custom endpoints for accessing stored media.
- Choosing how media is delivered in webhook events (Base64, S3 URL, or both).
Properties
| Name | Meaning |
|---|---|
| Access Key | The AWS S3 access key used for authentication. |
| 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: https://s3.amazonaws.com). |
| Media Delivery | How media is delivered in webhook events; options are: Base64 Only, S3 Only, Both Base64 and S3. |
| Path Style | Whether to use path-style URLs instead of virtual-hosted style URLs. |
| Public URL | A public URL prefix for accessing files, e.g., a CDN URL. |
| Region | The AWS region of the S3 bucket (default: us-east-1). |
| Retention Days | Number of days to retain files before they are deleted automatically. |
| Secret Key | The AWS S3 secret key used for authentication (input masked). |
Output
The node outputs JSON data representing the response from the API after configuring the S3 settings. This typically includes confirmation of the configuration status or any error messages returned by the backend service.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the DinastiAPI service managing WhatsApp sessions.
- Requires valid AWS S3 credentials (access key and secret key) with appropriate permissions for the specified bucket.
- The node expects the user to provide correct S3 endpoint and region information if using non-default AWS regions or compatible S3 services.
- No additional environment variables or n8n-specific configurations are explicitly required beyond standard API credential setup.
Troubleshooting
- Invalid Credentials: If the access key or secret key is incorrect or lacks permissions, the API request will fail. Verify AWS IAM permissions and keys.
- Bucket Not Found: Ensure the specified bucket exists in the given region and that the credentials have access to it.
- Endpoint Misconfiguration: Using an incorrect or unreachable S3 endpoint URL can cause connection failures. Confirm the endpoint URL matches your S3 provider.
- Retention Policy Issues: Setting retention days too low might lead to premature deletion of media files.
- Media Delivery Mismatch: Selecting an unsupported media delivery option may cause webhook events to not deliver media as expected.
- Common error responses from the API should be inspected in the node's execution logs to identify misconfigurations.
Links and References
- Amazon S3 Documentation
- AWS IAM User Guide
- DinastiAPI WhatsApp Session Management (if publicly available) (replace with actual link if known)