> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/integrations/how-daylite-connects-to-other-tools.md).

# How Daylite Connects to Other Tools

Daylite connects to external apps through built-in integrations, automation platforms like Zapier and Make.com, third-party add-ons, and a REST API.

Daylite connects to external apps and services through four methods: built-in integrations maintained by Marketcircle, automation platforms like Zapier and Make.com, third-party developer add-ons, and a REST API for custom development.

**Key facts:**

* Built-in integrations handle email, video conferencing, calendar sharing, and contact sharing directly within Daylite
* Automation platforms connect Daylite to thousands of other apps through triggers and actions
* Third-party add-ons extend Daylite with features Marketcircle does not provide directly
* The REST API lets developers build custom integrations programmatically
* A full list of available integrations is maintained on the [Daylite Integrations & Add-Ons](https://www.marketcircle.com/add-ons/) page

## Built-in integrations

Daylite integrates directly with apps for email, video conferencing, calendar sharing, and contact sharing. These features are built into Daylite and do not require an automation platform or add-on.

{% content-ref url="/pages/nCvdaUTcklWGCUnN2aFH" %}
[Built-in Integrations in Daylite](/help/mac-fundamentals/integrations/built-in-integrations-in-daylite.md)
{% endcontent-ref %}

## Automation

Automation platforms like Zapier and Make.com connect Daylite to other apps through triggers and actions. When something happens in one app, the platform automatically performs an action in another — for example, adding a new Daylite Contact to a mailing list.

{% content-ref url="/pages/bfex6heTpjjv6Y7fEiET" %}
[Automation in Daylite](/help/mac-fundamentals/integrations/automation-in-daylite.md)
{% endcontent-ref %}

## Third-party add-ons

Independent developers have built add-ons that extend Daylite with additional features. These are separate products with their own pricing and support.

{% content-ref url="/pages/2VHliTnGe0mwUrxWJUmL" %}
[Third-Party Add-Ons for Daylite](/help/mac-fundamentals/integrations/third-party-add-ons-for-daylite.md)
{% endcontent-ref %}

## API

The Daylite REST API provides programmatic access to Contacts, Companies, Opportunities, Projects, Tasks, Appointments, and other Daylite Objects. Developers can use the API to build custom integrations and workflows.

Use the API when an existing integration cannot support your workflow. It requires development resources to authenticate requests, handle data changes, and maintain the integration.

{% embed url="<https://developer.daylite.app/>" %}

***

## Frequently Asked Questions

**What is the difference between a built-in integration and a third-party add-on in Daylite?**

A built-in integration is developed and maintained by Marketcircle as part of the Daylite app — for example, video conferencing link support and calendar sharing. A third-party add-on is developed by an independent company and may have its own pricing, support, and update cycle.

**Where can I find the full list of apps that work with Daylite?**

The [Daylite Integrations & Add-Ons](https://www.marketcircle.com/add-ons/) page on the Marketcircle website maintains the complete list.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.daylite.app/help/mac-fundamentals/integrations/how-daylite-connects-to-other-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.