ClientifyInstall

Summary

Log a meeting or check-in against a Clientify contact by sending a POST request to the contact’s check-in endpoint. Provide the contact ID, type, comment, outcome, date, and owner; all six fields are required.

Inputs

• Contact ID (required) — Positive numeric ID of the contact to log the check-in for. Can be mapped from a previous step.
• Type (required) — Check-in type, sent as a string. Can be mapped from a previous step.
• Comment (required) — Check-in comment, sent as a string. Can be mapped from a previous step.
• Outcome (required) — Check-in outcome, sent as a string. Can be mapped from a previous step.
• Date (required) — Check-in date, sent as a string. Can be mapped from a previous step.
• Owner (required) — Positive numeric owner ID. Can be mapped from a previous step.

Output shape

One output item per input item, containing the Clientify response as JSON.

The response object is merged with an _meta object containing the resolved resource, operation, HTTP method, and request path. If the API returns an empty response, the item contains {"ok":true}; primitive responses are wrapped in {"data":...}. With Continue On Fail enabled, failed items instead contain success:false, operation, and error.

Links

• n8n community nodes installation guide