William CRM

Interact with William CRM API
Join our community

Actions2

Overview

This node integrates with the William CRM API to create new lead records. It is designed to help users automate the process of adding leads into their CRM system directly from n8n workflows. Typical use cases include capturing lead information from forms, marketing campaigns, or other data sources and automatically pushing that data into William CRM for sales follow-up.

For example, after collecting a visitor's contact details on a website, this node can be used to create a corresponding lead in William CRM without manual entry, ensuring timely and accurate lead management.

Properties

Name Meaning
Name The full name of the lead to be created.
Email The email address of the lead; required for identification and communication purposes.
Phone The phone number of the lead; optional but useful for direct contact.

Output

The node outputs an array of JSON objects, each representing the response from the William CRM API for the created lead. Each output item contains the full JSON response returned by the API, which typically includes details about the newly created lead record such as its ID and any metadata provided by the CRM.

No binary data is produced by this node.

Dependencies

  • Requires an active connection to the William CRM API.
  • Users must provide valid API credentials (an API key and API URL) configured in n8n to authenticate requests.
  • The node sends HTTP POST requests to the CRM’s API endpoint using these credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Missing required fields ("Name" or "Email") will likely result in API errors.
    • Network connectivity problems may prevent successful API calls.

  • Error messages:

    • Errors returned from the API are captured and included in the output if the node is set to continue on failure.
    • Common error messages might indicate invalid input data or authorization failures.

  • Resolution tips:

    • Verify that the API key and URL are correctly configured in n8n credentials.
    • Ensure all required properties are provided and correctly formatted.
    • Check network access and firewall settings to allow outbound API requests.

Links and References

Discussion