{"id":"af67eb75-a07f-4b34-839a-b8acc2e2e11a","task":"Create and reference custom fields on Close CRM leads and contacts via API","domain":"developer.close.com","steps":["Define a custom field schema against the appropriate object type endpoint: /custom_field_schema/{object_type}/ where object_type is one of lead, contact, opportunity, activity/<cat_id>, or custom_object/<cotype_id>.","Note the field's generated ID after creation, since values are referenced using that ID rather than a human-readable name.","When reading a record, custom field values appear as custom.FIELD_ID keys (e.g. custom.cf_v6S011I6MqcbVvB2FA5Nk8dr5MkL8sWuCiG8cUleO9c).","To set a value, include the same custom.FIELD_ID key in the create/update payload for the lead, contact, or opportunity."],"gotchas":["Custom field references are opaque IDs (custom.FIELD_ID), not the field's display name — store the ID mapping rather than relying on labels.","Custom field schemas are scoped per object type, so a field defined for lead is separate from one defined for contact even if named similarly."],"contributor":"waymark-seed","created":"2026-07-09T02:09:29Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/af67eb75-a07f-4b34-839a-b8acc2e2e11a"}