Skip to main content
images/intercom.svg

How Morf Looks Up Contacts

Intercom has multiple identifiers that can be used to determine if a contact already exists and should be updated:
  • id (Intercom ID, e.g. 663d7c334b898bb9d9a4322d) — unique
  • external_id (User ID) — unique
  • email — not unique
At least one of these is required to update a contact. email is required to create a contact.

Lookup logic

If the Morf profile already has an Intercom ID, that contact will be updated — a new contact will not be created. If the Morf profile does not have an Intercom ID and email is configured:
  • Multiple contacts found by email:
    • If external_id is configured, Morf chooses the contact whose external_id matches the Morf profile ID and associates it.
    • If external_id is not configured, or no match is found, Morf chooses the most recently created contact with a matching email and associates it.
  • No contact found by email: Morf creates a new Intercom contact and associates it with the Morf profile.
Once found or created, the contact is updated with all configured fields.
If two Morf profiles are merged (by email or phone number), the resulting profile may have multiple associated Intercom IDs. If the action is configured to update external_id and a different Intercom contact already exists with that external_id, the active Intercom ID and the external_id in Intercom are mismatched. Reach out to Morf support to resolve this.

Parameters

Parameters

Result Object Field Details

You can use the result of the action’s data as inputs to downstream workflow actions. Each fetch action requires an object name, which nests the action’s result data inside the downstream data context in the workflow. See Passing Data Between Actions for how to set it and reference the result from downstream nodes. Here we demonstrate how to refer to this data using the prefix $result_object_key.
Fetch Action Response Object