izapp - WhatsApp icon

izapp - WhatsApp

Interação com a Plataforma de Relacionamento via WhatsApp - IZapp
Join our community

Actions58

Overview

This node integrates with the IZapp platform to interact with WhatsApp-related services and other customer relationship features. Specifically, for the operation "Usuário - Agenda - Listar" (User - Schedule - List), it retrieves the schedule events of a specified operator within a given date range and supports pagination.

Common scenarios where this node is beneficial include:

  • Automating retrieval of an operator's calendar or agenda events for reporting or synchronization.
  • Integrating operator schedules into broader workflows, such as sending reminders or allocating resources based on availability.
  • Monitoring operator activity periods in customer support or sales teams.

Example use case:

  • A workflow that fetches all scheduled events for a customer service operator between July 1, 2020, and October 10, 2020, to generate daily summaries or trigger notifications.

Properties

Name Meaning
ID do Operador The unique identifier of the operator whose schedule events you want to retrieve.
Data Inicial The start date of the period to query the schedule, formatted as YYYY-MM-DD.
Data Final The end date of the period to query the schedule, formatted as YYYY-MM-DD.
Página The page number of the schedule events list to retrieve, starting from 1.

Output

The node outputs JSON data representing the schedule events of the specified operator within the requested date range and page. The structure typically includes event details such as dates, times, descriptions, and possibly identifiers related to each scheduled item.

If binary data were involved (not indicated here), it would represent attachments or media related to schedule events, but this operation focuses on JSON event data only.

Dependencies

  • Requires an API key credential to authenticate with the IZapp platform.
  • Depends on the IZapp API endpoints for fetching operator schedules.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid Operator ID: If the operator ID is incorrect or does not exist, the API may return an error or empty results. Verify the operator ID before running the node.
  • Date Format Errors: Dates must be in YYYY-MM-DD format. Incorrect formats can cause request failures or unexpected results.
  • Pagination Issues: Requesting a page number beyond available pages may return empty results. Adjust the page number accordingly.
  • Authentication Failures: Ensure the API key credential is valid and has sufficient permissions to access operator schedules.
  • Network or API Downtime: Temporary connectivity issues or API outages will cause errors; retry after some time.

Links and References

Discussion