BookedIn icon

BookedIn

Interact with BookedIn AI agents, leads, campaigns, strategies, lists, and human messaging
Join our community

Actions29

Overview

The node provides integration with the BookedIn platform, allowing users to manage leads among other resources. Specifically, the Lead - Update operation enables updating details of an existing lead in the BookedIn system. This is useful for keeping lead information current, such as correcting contact details, adding metadata, or changing the lead source.

Common scenarios include:

  • Updating a lead’s contact information after receiving new data.
  • Correcting typos or errors in lead names or emails.
  • Adding custom metadata fields to enrich lead profiles.
  • Changing the lead source to reflect how the lead was acquired.

Example: You have a lead with ID ld_f1e2d3c4b5a6 whose phone number and timezone have changed. Using this node, you can update those fields to keep your CRM data accurate.

Properties

Name Meaning
Lead ID The unique identifier of the lead to update (required).
First Name Lead's first name.
Last Name Lead's last name.
Email Lead's email address.
Phone Number Lead's phone number in international format; must start with "+" and contain only digits after it.
Timezone Lead's timezone, e.g., "Europe/Madrid".
Source Source of the lead. Options: API, Import, Manual, Website.
Custom Fields (Meta) Additional metadata as a JSON object, e.g., {"campaign": "summer2024", "priority": "high"}.

Output

The node outputs a JSON object representing the updated lead as returned by the BookedIn API. This typically includes all lead fields such as ID, contact details, source, timezone, and any metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the BookedIn API.
  • The node makes HTTP requests to https://api.bookedin.ai/api/v1/leads/{leadId} using PUT method.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Phone Number Validation Errors:
    The phone number must be in international format starting with "+", contain only digits after "+", and be between 7 and 15 digits long.
    Error messages:

    • "Phone number is required"
    • "Phone number must be in international format starting with +"
    • "Phone number must contain only digits after the + sign"
    • "Phone number must be at least 7 digits long"
    • "Phone number is too long"
      Resolution: Ensure the phone number meets these criteria before updating.

  • Invalid Email Format:
    If the email does not match a standard email regex pattern, an error is thrown.
    Resolution: Provide a valid email address.

  • Invalid JSON in Meta Field:
    The meta field must be valid JSON.
    Error message: "Invalid JSON format in meta fields"
    Resolution: Check and correct the JSON syntax.

  • No Fields to Update:
    If no updatable fields are provided, the node throws an error.
    Error message: "At least one field must be provided to update a lead"
    Resolution: Provide at least one field to update.

  • API Errors:
    Errors from the BookedIn API (e.g., invalid lead ID, authentication failure) will be propagated.
    Resolution: Verify the lead ID exists and the API credentials are correct.

Links and References

If you need further details on other operations or resources, feel free to ask!

Discussion