> 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/third-party-add-ons-for-daylite.md).

# Third-Party Add-Ons for Daylite

Extend Daylite with third-party add-ons from independent developers, like iOSXpert ProductivityTools — each with its own pricing, support, and licensing.

Third-party add-ons are products built by independent developers that extend Daylite with features Marketcircle does not provide directly. These are separate products with their own pricing, licensing, and support — you work with the add-on developer for setup and troubleshooting.

**Key facts:**

* Third-party add-ons are developed and maintained by independent companies, not Marketcircle
* iOSXpert ProductivityTools is the most established add-on suite for Daylite
* Add-ons connect to Daylite through the REST API
* Each add-on has its own pricing, installation process, and support channels
* A current list of available add-ons is maintained on the [Daylite Integrations & Add-Ons](https://www.marketcircle.com/add-ons/) page

***

## iOSXpert ProductivityTools for Daylite

iOSXpert ProductivityTools is the most widely used third-party add-on suite for Daylite. It extends Daylite with additional tools for conferencing, scheduling, templates, and more.

iOSXpert is a separate company from Marketcircle. For pricing, installation, and support, visit the [iOSXpert website](https://iosxpert.biz/en/).

{% embed url="<https://iosxpert.biz/en/plugins-for-daylite/productivitytools/>" %}

***

## Other Third-Party Add-Ons for Daylite

Other third-party tools are available through the [Daylite Integrations & Add-Ons](https://www.marketcircle.com/add-ons/) page. These include tools for email marketing, accounting, invoicing, and other business workflows.

Because third-party add-ons are maintained by their developers, availability, features, and compatibility may change. Check the add-on developer's website for the most current information.

{% embed url="<https://www.marketcircle.com/add-ons/>" %}

***

## Frequently Asked Questions

**Who do I contact for support with a third-party add-on?**

Contact the add-on developer directly. Marketcircle does not provide support for third-party products. Each add-on has its own support channels listed on the developer's website.

**How do third-party add-ons connect to Daylite?**

Most add-ons use the Daylite REST API to read and write data. Installation and authentication steps vary by add-on — refer to the developer's documentation for setup instructions.

**Are third-party add-ons included in my Daylite subscription?**

No. Third-party add-ons are separate products with their own pricing. Your Daylite subscription covers the Daylite app and built-in integrations only.


---

# 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/third-party-add-ons-for-daylite.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.