SteveChat icon

SteveChat

Interact with SteveChat API for WhatsApp messaging

Overview

The node "SteveChat" enables interaction with the SteveChat API, specifically designed for WhatsApp messaging. It supports various user-related operations such as checking WhatsApp status, retrieving user info, sending presence updates, getting avatars, and fetching profiles. This node is beneficial in automation workflows where you need to programmatically verify or retrieve information about WhatsApp users by their WhatsApp ID.

A practical example includes verifying if a specific WhatsApp user (identified by their phone number) is active or reachable before sending messages or notifications through an automated system.

Properties

Name Meaning
User ID The WhatsApp user ID, which is the phone number followed by @s.whatsapp.net. For example: 5511999999999@s.whatsapp.net. This identifies the target WhatsApp user for the operation.

Output

The output of the node is a JSON object containing the result of the selected operation on the specified WhatsApp user. The exact structure depends on the operation performed but generally includes user-related data retrieved from the SteveChat API.

If the node encounters an error during execution, the output JSON will contain an error field with the error message describing what went wrong.

The node does not explicitly handle binary data outputs.

Dependencies

  • Requires an API key credential for authenticating with the SteveChat API.
  • The node depends on the external SteveChat service that provides WhatsApp messaging capabilities.
  • Proper configuration of the API authentication credentials within n8n is necessary for successful operation.

Troubleshooting

  • Common Issues:

    • Invalid or missing WhatsApp user ID format (must be phone number + @s.whatsapp.net).
    • Network or authentication errors when connecting to the SteveChat API.
    • Unsupported resource or operation names if misconfigured in the node parameters.
  • Error Messages:

    • "The resource \"user\" is not supported!": Indicates the resource parameter is invalid or not implemented.
    • "The operation \"checkWhatsApp\" is not supported for resource \"user\"!": Means the operation name is incorrect or unavailable for the chosen resource.
    • Errors returned from the API will appear in the error field of the output JSON; check the message for details.
  • Resolutions:

    • Verify the WhatsApp user ID format matches the expected pattern.
    • Ensure the API key credential is correctly set up and has proper permissions.
    • Double-check resource and operation names in the node configuration.
    • Enable "Continue On Fail" option to allow workflow continuation despite individual item errors.

Links and References

Discussion