Actions15
- Create Newsletter
- Get Newsletter Info
- Send Newsletter Message
- Subscribe Newsletter
- Subscribe with Invite
- Unsubscribe Newsletter
- Unsubscribe with Invite
- Mute Newsletter
- Get Newsletter Messages
- Send Newsletter Reaction
- Mark Newsletter Viewed
- Subscribe Live Updates
- Get Message Updates
- Accept TOS Notice
- Send Admin Invite
Overview
This node integrates with the ZuckZapGo API to manage WhatsApp newsletters and channels. It supports a wide range of operations such as listing newsletters, creating new ones, subscribing/unsubscribing, sending messages or reactions, muting notifications, retrieving messages, and accepting terms of service notices.
The "Accept TOS Notice" operation specifically allows users to accept a terms of service (TOS) notice by providing a notice ID and stage. This is useful in workflows where compliance with updated terms is required before proceeding with other newsletter management actions.
Practical example:
A user can automate the acceptance of updated terms of service for a newsletter before sending out messages or managing subscriptions, ensuring that all legal requirements are met programmatically.
Properties
| Name | Meaning |
|---|---|
| Notice ID | The identifier of the terms of service notice to accept. Default is "20601218". |
| Stage | The stage number for the TOS acceptance process. Default is "5". |
Output
The node outputs JSON data representing the response from the ZuckZapGo API for the "acceptTOSNotice" operation. This typically includes confirmation of the acceptance status or any relevant metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the ZuckZapGo API via an API key credential configured in n8n.
- The node depends on the
zuckzapgoApiRequesthelper function to make HTTP requests to the API endpoints. - Proper API credentials must be set up in n8n to authenticate requests.
Troubleshooting
Common issues:
- Invalid or expired API credentials may cause authentication failures.
- Providing incorrect or missing
noticeIdorstageparameters can result in API errors. - Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the API will be included in the node's output if "Continue On Fail" is enabled.
- Typical error messages might indicate invalid notice IDs or unauthorized access; verify input values and credentials.
- To resolve, ensure correct parameter values and valid API credentials are used.
Links and References
- ZuckZapGo API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes