Wortic icon

Wortic

Interact with Wortic CRM API - Complete automation for leads, clients, projects, invoices, support tickets and calendar events

Actions12

Overview

This node integrates with the Wortic CRM API to manage calendar events. Specifically, the Update operation for the Calendar resource allows users to modify existing calendar events by specifying their ID and updating details such as title, description, start date, and end date.

Common scenarios where this node is beneficial include:

  • Automatically updating event details in a CRM calendar when changes occur elsewhere (e.g., rescheduling meetings).
  • Synchronizing external calendar updates into Wortic CRM.
  • Bulk updating multiple calendar events programmatically within an automation workflow.

For example, you could use this node to update the time or description of a scheduled appointment after receiving new information from a client.

Properties

Name Meaning
Title The title of the calendar event.
Description A textual description providing more details about the event.
Start Date The starting date and time of the event (in ISO 8601 format).
End Date The ending date and time of the event (in ISO 8601 format).
ID The unique identifier of the calendar event record to update.

Output

The node outputs JSON data representing the response from the Wortic CRM API after attempting to update the calendar event. This typically includes the updated event details or confirmation of the update.

The output structure is:

{
  "json": {
    // Response object from Wortic CRM API containing updated event data
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Wortic CRM API.
  • Needs an API key credential configured in n8n for authentication.
  • The node sends HTTP POST requests to the API URL specified in the credentials.
  • Proper permissions on the API key to update calendar events are necessary.

Troubleshooting

  • Invalid or missing ID: If the provided event ID does not exist or is incorrect, the API will likely return an error. Verify the ID before running the update.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • Date format issues: The start and end dates must be valid ISO 8601 datetime strings; otherwise, the API may reject the request.
  • API URL misconfiguration: Confirm that the base URL in the credentials is correct and reachable.
  • Partial updates: All required fields (title, start_date, end_date) must be provided; missing required fields can cause errors.

If the node throws an error, enabling "Continue On Fail" can help process other items while logging errors for problematic ones.

Links and References

  • Wortic CRM official API documentation (refer to your API provider's docs for exact endpoints and payloads)
  • n8n HTTP Request node documentation for understanding how HTTP calls are made
  • ISO 8601 date and time format specification: https://en.wikipedia.org/wiki/ISO_8601

Discussion