Sendtick icon

Sendtick

Interact with Sendtick API for WhatsApp messaging
Join our community

Actions5

Overview

This node integrates with the Sendtick API to interact with WhatsApp messaging services. Specifically, for the Session - Get operation, it retrieves detailed information about a particular WhatsApp session by its Session ID. This is useful when you want to monitor or manage active WhatsApp sessions linked to your Sendtick account.

Practical examples include:

  • Fetching the status and metadata of a specific WhatsApp session.
  • Verifying if a session is active before sending messages.
  • Auditing session details for troubleshooting or reporting.

Properties

Name Meaning
Session ID The unique identifier of the WhatsApp session to retrieve. This is required to specify which session's details to fetch.

Output

The output is a JSON object containing the details of the requested WhatsApp session as returned by the Sendtick API. This typically includes session metadata such as session status, creation time, associated phone number, and other relevant session attributes.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "string",
  "status": "string",
  "phoneNumber": "string",
  "createdAt": "string",
  "updatedAt": "string",
  // ... other session-specific fields
}

Dependencies

  • Requires an API key credential for authenticating with the Sendtick API.
  • The node uses the base URL https://sendtick.co/api/v1.
  • Proper configuration of the Sendtick API credentials in n8n is necessary.

Troubleshooting

  • Missing Session ID: If the Session ID property is not provided, the node will throw an error indicating that the sessionId is required.
  • Invalid Session ID: If the provided Session ID does not exist or is invalid, the API may return an error or empty response.
  • Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network Issues: Connectivity problems to the Sendtick API endpoint can cause request failures.
  • Unsupported Resource/Operation: Using unsupported combinations of resource and operation will result in an error.

To resolve errors:

  • Double-check the Session ID value.
  • Verify API credentials and permissions.
  • Confirm network connectivity.
  • Review the node parameters to ensure correct resource and operation selection.

Links and References

Discussion