Dalil AI icon

Dalil AI

Consume Dalil AI API

Actions40

Overview

This node integrates with the Dalil AI API to manage "Person" records within a CRM or contact management system. Specifically, the Update Person operation allows users to modify existing person entries by specifying their unique identifier and the fields to update.

Common scenarios for this node include:

  • Updating contact details such as email addresses, phone numbers, job titles, or location.
  • Modifying associations like company affiliation or ownership.
  • Adjusting custom properties tailored to your workspace needs.
  • Refreshing social media profile links (LinkedIn, X/Twitter).
  • Controlling the depth of related data returned with the update.

Practical example:

  • A marketing automation workflow updates a person's city and job title after receiving new information from a lead capture form.
  • A sales process updates the primary email and owner ID of a contact when reassigned to a different team member.

Properties

Name Meaning
Person ID UUID string identifying the person record to update.
Update Fields Collection of fields to update on the person record. Includes:
- Additional Emails: List of extra email addresses.
- Avatar URL: Link to avatar image.
- City: City of residence or work.
- Company ID: UUID of associated company.
- Custom Properties: Workspace-specific custom fields with values depending on field type (text, rating, multi-select, etc.).
- First Name: Person's first name.
- Job Title: Position or role.
- Last Name: Person's last name.
- LinkedIn Label: Display label for LinkedIn profile.
- LinkedIn URL: URL to LinkedIn profile.
- Owner ID: UUID of responsible team member.
- Primary Email: Main email address.
- Primary Phone Calling Code: International calling code with plus prefix.
- Primary Phone Country Code: Two-letter country code.
- Primary Phone Number: Phone number without country code.
- X (Twitter) Label: Display label for X profile.
- X (Twitter) URL: URL to X profile.
Depth Name or ID Level of nested related objects to include in the response:
- 0: Only the person object.
- 1: Person plus directly related objects.
- 2: Person, direct relations, and their relations.

Output

The output is a JSON object representing the updated person record as returned by the Dalil AI API. It includes all updated fields and may contain nested related objects depending on the specified depth level.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "uuid-string",
  "name": {
    "firstName": "John",
    "lastName": "Doe"
  },
  "emails": {
    "primaryEmail": "[email protected]",
    "additionalEmails": ["[email protected]"]
  },
  "avatarUrl": "https://example.com/avatar.jpg",
  "city": "New York",
  "companyId": "company-uuid",
  "customProperty1": "value",
  "linkedinLink": {
    "primaryLinkUrl": "https://linkedin.com/in/johndoe",
    "primaryLinkLabel": "Professional Profile",
    "secondaryLinks": []
  },
  "xLink": {
    "primaryLinkUrl": "https://x.com/johndoe",
    "primaryLinkLabel": "Twitter Handle",
    "secondaryLinks": []
  },
  "ownerId": "owner-uuid",
  ...
}

Dependencies

  • Requires an active connection to the Dalil AI API.
  • Needs an API key credential configured in n8n for authentication.
  • The node uses HTTP methods (PATCH) to update person records via REST endpoints.
  • Custom properties depend on metadata fetched dynamically from the API; thus, the workspace must have these custom fields defined.

Troubleshooting

  • Invalid Person ID: If the provided UUID does not correspond to an existing person, the API will return an error. Verify the Person ID is correct.
  • Invalid Custom Property Metadata: Errors can occur if custom property metadata is malformed or missing. Ensure custom properties are correctly selected and formatted.
  • Invalid Field Values: Some fields require specific formats (e.g., valid email format, URLs starting with http/https). Invalid inputs will cause errors.
  • API Authentication Failures: Check that the API key credential is valid and has sufficient permissions.
  • Depth Parameter Issues: Providing an invalid depth value may result in unexpected responses or errors. Use only 0, 1, or 2 as allowed.
  • Network or API Downtime: Temporary connectivity issues or API outages will cause request failures.

To resolve errors:

  • Double-check input parameters for correctness.
  • Review API credentials and permissions.
  • Consult API documentation for field requirements.
  • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion