I believe an API is a key component if Orchestra aims for widespread agency adoption. Agencies like mine use many tools (e.g., email, incident tracking software, and monitoring software), and the only way to maintain efficiency is to integrate these tools to create a single source of truth. Furthermore, some clients are hesitant to adopt new tools (such as a client portal) and prefer to use email. Therefore, building workflows to push emails to Orchestra as new tasks would be incredibly beneficial. I understand that Zapier integration is a priority, but for some agencies, the lack of an API could be a significant obstacle due to the availability of API-compatible applications like the open-source ActivePieces, N8N, and Pabbly. API access would be more system-agnostic, enabling the quick implementation of automations. I look forward to hearing updates on the progress of this component.

OOOO PLEASE Have this!! AgencyHandy has this and their API is not good. It has bad docs (swaggerUI) that doesn't work for testing, and doesn't bring clear intent. We would like to create a client via API after a form is filled.