Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node allows updating a department within a WhatsApp management system via the Wassenger API. It is useful for organizations that manage multiple departments linked to different WhatsApp numbers and want to modify department details such as name, color, icon, description, or assigned agents dynamically.

Typical use cases include:

  • Renaming a department to reflect organizational changes.
  • Changing the department's color or icon for better visual identification in dashboards.
  • Updating the list of agents assigned to a department to reflect staffing changes.
  • Modifying the department description to provide updated information.

For example, a customer support team might update the "Technical Support" department's color to "Emerald" and add new agents after hiring.

Properties

Name Meaning
WhatsApp Number (device) The ID of the WhatsApp number associated with the department. This identifies which WhatsApp account the department belongs to.
Department ID (department) The unique identifier of the department to update. Required to specify which department is being modified.
Name (name) New name for the department. Should be between 2 and 25 characters.
Color (color) New color for the department used for quick visual identification. Options include Ruby, Tomato, Orange, Sunflower, Bubble, Rose, Poppy, Rouge, Raspberry, Purple, Lavender, Violet, Pool, Emerald, Kelly, Apple, Turquoise, Aqua, Gold, Latte, Cocoa, Iron.
Icon (icon) New icon identifier representing the department visually. Options include Briefcase, Users, User Tie, Chart Bar, Clipboard List, Comments, Headset, User Cog, User Edit, User Friends, Laptop Code, Network Wired, Building, Handshake, Address Book, Layer Group, Project Diagram, Calendar Check, Clipboard Check, Tasks, Chart Pie, Hands Helping, Shield Alt, User Lock, User Shield, Bullhorn, Comments Dollar, Comment Dots, Fingerprint, Check Circle, Chalkboard Teacher, Cogs, Rocket, Drafting Compass, Lightbulb, Envelope, Inbox, People Carry, Code Branch, Globe, Hand Holding USD, Money Bill Wave, Phone, Wrench, Balance Scale, Thumbs Up, User Secret, User Graduate, Landmark, Archive.
Description (description) New textual description of the department, up to 300 characters.
Agents (agents) New list of agent IDs to assign to the department. Must include between 1 and 30 agents.

Output

The node outputs JSON data representing the updated department object returned by the Wassenger API. This typically includes the department's current state after the update, such as its ID, name, color, icon, description, and assigned agents.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Wassenger WhatsApp API using a valid API key credential configured in n8n.
  • The node depends on dynamic loading methods to fetch available WhatsApp numbers (getDevices), departments (getDepartments), and agents (getTeamAgents) based on the selected WhatsApp number.
  • Proper permissions and API access rights are necessary to update department information.

Troubleshooting

  • Common issues:

    • Invalid or missing WhatsApp number ID or department ID will cause the update to fail.
    • Providing invalid values for properties like name length outside 2-25 characters or description exceeding 300 characters may result in validation errors.
    • Assigning fewer than 1 or more than 30 agents will likely trigger an error.
    • Network or authentication errors if the API key is incorrect or lacks required scopes.

  • Error messages:

    • "Department not found": Verify the department ID corresponds to an existing department under the specified WhatsApp number.
    • "Invalid parameter": Check that all input fields meet the expected format and constraints.
    • "Unauthorized" or "Authentication failed": Confirm the API key credential is correctly set up and has sufficient permissions.

  • To resolve errors, ensure all required parameters are provided and valid, check API credentials, and verify network connectivity.

Links and References

Discussion