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 leads, clients, calendar events, and other resources. Specifically for the Lead - Update operation, it updates an existing lead record in the CRM system by sending updated information such as name, email, phone number, and company details.

Typical use cases include:

  • Keeping lead information current after receiving new contact details.
  • Correcting or enriching lead data automatically from other systems.
  • Synchronizing lead updates from external sources into Wortic CRM.

For example, if a sales team receives updated contact info for a lead, this node can be used in an automation workflow to update that lead’s record in Wortic CRM without manual entry.

Properties

Name Meaning
ID The unique identifier of the lead record to update.
Name The full name of the lead.
Email The lead's email address.
Phone The lead's phone number (optional).
Company The company associated with the lead (optional).

Output

The node outputs the JSON response returned by the Wortic CRM API after attempting to update the lead. This typically includes the updated lead data or confirmation of the update operation.

The output structure is:

{
  "json": {
    // Response object from Wortic CRM API representing the updated lead
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Wortic CRM API.
  • The node expects the base URL of the Wortic API to be configured in the credentials.
  • HTTP POST requests are made to the API endpoint with JSON payloads.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Providing an incorrect or non-existent lead ID will result in errors from the API.
    • Missing required fields like name or email will cause validation errors.

  • Error messages:

    • Authentication errors usually indicate invalid credentials; verify the API key and base URL.
    • Validation errors from the API will specify which fields are missing or malformed.
    • Network or connectivity issues may cause request timeouts or failures.

  • Resolution tips:

    • Ensure all required properties (ID, Name, Email) are provided.
    • Confirm the API key and base URL are correctly set in the node credentials.
    • Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.

Links and References

  • Wortic CRM API Documentation (refer to official Wortic API docs for detailed endpoints and data formats)
  • n8n HTTP Request Node documentation (for understanding how HTTP calls are made within n8n)

Discussion