Endearist
DE EN – switch to German Get Endearist

Integrations

What Endearist connects to.

This list is shorter than our rivals’, and that is not an oversight. Every integration is a copy of your data somewhere else.

A personal CRM that connects to everything is a personal CRM whose vendor sees everything. Endearist has not launched yet. Planned connections are intended to run through your device, not our server. The final group explains which ones we deliberately refuse.

Planned for v1

In v1

Endearist has not launched yet. This is the planned scope of the first release; connections are intended to run through your device.

  • Google Contacts, Apple Contacts, Outlook — import

    Via vCard or CSV. Names, emails, phone numbers, companies, and tags carry across. An import, not standing access to your account.

  • Your own folder or WebDAV as the sync target

    Sync over a local or shared folder or WebDAV is planned for v1. Content is intended to be encrypted on your device before it leaves.

  • Your own AI key

    OpenAI, Anthropic, or Gemini. The key stays on your device and the request goes straight from you to the provider. Without a key the app works fully, just without AI.

  • Markdown export into everything else

    The most reliable integration is the one you do not need. Plain Markdown is read by Obsidian, Notion, Bear, git, and every text editor of the last thirty years.

After v1

Planned after v1

An operated sync service is outside the first release scope.

  • Managed sync on Endearist Cloud

    This service is planned for after v1, as part of the Pro Cloud subscription only. Content is intended to be encrypted on your device before upload.

Undecided

Not decided yet

These ideas are not scheduled. Their status follows the app capability registry.

  • Google Drive as a sync target

    Google Drive as a destination is not decided yet.

  • Calendar read (Google, Apple, Outlook)

    A read-only calendar overlay is not decided yet. Birthdays and appointments would appear beside their contact without writing back to your calendar.

  • Capture from your local calendar

    Not just showing appointments but inferring who you actually met, so the warmth score stays right without you typing anything. The calendar is already on your device; this needs no server.

  • Mobile share sheet

    Deliberately attach a message from WhatsApp, Signal, or Mail to a contact. You decide message by message; nothing reads along in the background.

Later

Possible later

Not ruled out, but only in a shape that does not hollow out the local store.

  • Local webhooks / CLI

    Automation that runs on your machine instead of in an automation vendor’s cloud. Most of what people use Zapier for could be built this way.

  • CalDAV / CardDAV

    Open protocols instead of individual vendor APIs — a sync path that still works after a vendor turns its API off.

Never

Deliberately not connected

Every one of these requires your contacts to sit on a server we can read. That is the point where local-first stops being a promise.

If one of these connections is decisive for you, Endearist is honestly the wrong tool — and our comparison pages will tell you which one is the right one.

  • LinkedIn sync and job-change alerts

    Dex’s most-praised feature, and we do not have it. It requires either scraping your LinkedIn account or a server holding your connections permanently. If you network professionally and need it, Dex is the more honest tool for you.

  • Automatic reading of email and messengers

    Mesh, Clay, Cloze, and Wend build their history this way, and it is more complete than ours because of it. The price is a mailbox grant that sees everything, including the messages that have nothing to do with your address book.

  • Public-web enrichment

    Automatically re-researching contacts means building a dossier on somebody who does not know about it. We will not build it, not even as an opt-in, because the person affected is not the one giving consent.

  • Zapier, Make, and other hosted automation

    A Zapier connector would mean shipping your contacts to a third vendor so it can pass them on. The local route above is the answer we would rather build.

  • A public cloud API over your contacts

    folk and others have one, and for teams that makes sense. An API presupposes the data sitting on a reachable server, which is exactly what we avoid.