Public API and webhook access

Status: planned. This isn't available yet. Which endpoints are included and when it ships are still being worked out, so nothing here is a commitment on scope or timing. The problem Some businesses run their own tools and scheduled jobs alongside their CRM. Without a public API, they can't keep those workflows going, and that's a blocker for switching to TalleFlow. MCP access helps for AI tools, but it doesn't replace a standard API for jobs running on your own server. What customers are asking for Read and write API access to core TalleFlow data, including: Leads, proposals, and bookings Payments and expenses Availability and appointment slots Venues and staff Notes Packages and backdrops Questionnaires and contracts Design and template status Webhooks that fire when key things happen, such as: A new lead comes in A payment is made A contract is signed Lead capture from outside TalleFlow: connect lead forms on external landing pages (like ad campaign pages) and your own business website, so each submission automatically creates a lead and project in TalleFlow. Why it matters Keep your existing automations and scheduled jobs when you move to TalleFlow Get leads from every source into one pipeline without copying them by hand React in real time to new leads, payments, and signed contracts Vote and comment with the endpoints or events that matter most to your business. It helps us decide what to build first.