twenty icon indicating copy to clipboard operation
twenty copied to clipboard

Make Contacts Searchable by Email Addresses

Open inside-mo opened this issue 5 months ago • 2 comments

Scope & Context

Enable people / contacts to be searched for by their email addresses via the API and make their UUID an optional requirement instead of a mandatory one. Reason: When connecting other services to Twenty in the attempt to log certain with certain contacts, searching by the UUID is impractical. The UUID is unique to Twenty. But email addresses are a far more common unique identifier that can be shared among services that Twenty users will want to integrate.

Current behavior

A clear and concise description of what the current behavior is.

People / Contacts can only be searched for, if their UUID is known (mandatory).

Expected behavior

I can identify contacts by searching for their email addresses.

Technical inputs

I understand the risk of duplicates causing errors and producing search results with more than one result. But there needs to be a way to find contacts other than with their UUID

inside-mo avatar Jun 30 '25 11:06 inside-mo

Hello, may i take this up ? @inside-mo

ReesavGupta avatar Jun 30 '25 11:06 ReesavGupta

Hello, may i take this up ? @inside-mo

Please do :-).

inside-mo avatar Jun 30 '25 11:06 inside-mo

Hello @inside-mo, are you talking about your workspace members or people from the people standard object data model ? Please share either:

  • Request that assert your issue
  • UI video reproduction

Btw you're already able to filter people records using their email :)

prastoin avatar Jul 02 '25 16:07 prastoin

Closing from now

prastoin avatar Jul 02 '25 16:07 prastoin

@prastoin Hi. I actually meant the contact-object. So the persons associated with accounts and opportunities. Best of my knowledge and according to the documentation, I can only call upon them via API if have their UUID. Now assuming somebody books a meeting with me via a calendar app and I want to log that in Twenty: I can't do it because I have no way of identifying the leads UUID. Their email address, on the hand, is readily available. So if I can identify them that way via the API, I can start automating things.

inside-mo avatar Jul 02 '25 16:07 inside-mo

UI

Image

Using graphql API

Image

{
  "filter": {
    "or": [
      {
        "emails": {
          "primaryEmail": {
            "ilike": "%jone%"
          }
        }
      },
      {
        "emails": {
          "additionalEmails": {
            "like": "%jone%"
          }
        }
      }
    ]
  },
  "orderBy": [
    {
      "position": "AscNullsFirst"
    }
  ]
}

Hoping this answers your question ! Have a nice day

prastoin avatar Jul 02 '25 16:07 prastoin

REST API

Image

prastoin avatar Jul 02 '25 16:07 prastoin