Actions8
Overview
This node integrates with the Signal CLI API to manage Signal groups. Specifically, the "Group - List" operation retrieves a list of groups associated with a specified Signal account. This is useful for workflows that need to fetch and process group information from Signal, such as monitoring group memberships or automating group-related messaging tasks.
Practical example: You might use this node to periodically list all Signal groups for an account and then trigger further actions based on group data, like sending notifications or archiving group details.
Properties
| Name | Meaning |
|---|---|
| Account | The Signal account identifier (string) for which to list groups. |
Output
The node outputs JSON data containing the response from the Signal CLI API's listGroups method. The structure typically includes details about each group associated with the specified account, such as group IDs, names, and members.
Example output JSON structure:
{
"jsonrpc": "2.0",
"result": [
{
"groupId": "some-group-id",
"name": "Group Name",
"members": ["member1", "member2"]
},
...
],
"id": "uuid"
}
No binary data is produced by this operation.
Dependencies
- Requires access to the Signal CLI API endpoint URL configured in the node credentials.
- Needs an API key or authentication token set up in the credentials to authorize requests to the Signal CLI API.
- Uses HTTP POST requests to communicate with the Signal CLI API.
Troubleshooting
- Missing API URL: If the Signal CLI API URL is not set in the credentials, the node will throw an error indicating this. Ensure the API URL is correctly configured.
- API Communication Errors: Network issues or incorrect credentials can cause request failures. Check connectivity and credential validity.
- Invalid Account Parameter: Providing an invalid or empty account string may result in no groups returned or API errors.
- Unexpected API Response: If the API changes or returns unexpected data, the node might fail to parse the response properly.