There are now two useful ways to connect client management with Maroo. You can use Maroo’s built-in leads and CRM workflow, or keep an external CRM and connect it to Maroo for invoicing and payments. This article focuses on the second path through wedding photographer Jake Tenney’s external-CRM case study.
Wedding photographer and seasoned Táve user Jake Tenney of Sweetlife Photography built a workflow to pass client and invoice details from his external CRM into Maroo. We asked Jake to share the setup in a bonus webinar. Because this is a case study, compare its steps with Maroo’s current integration options before rebuilding it.
Start by choosing the operating model that fits your business. If you want lead capture, pipeline stages, ownership, notes, and statuses inside one system, Maroo CRM supports that path. If another CRM already anchors your process, keep it and connect the financial handoff to Maroo. The rest of this article shows the external-CRM approach.
Three steps to integrating your external CRM with Maroo
If your external CRM can send emails or trigger connected apps, you can adapt Jake’s approach. Treat the original steps as a pattern, then confirm the currently supported connectors and fields before implementing it.
Think of Zapier as a connector that moves information between systems according to rules you set. Review Maroo’s current integrations to choose a supported path, and confirm any third-party plan requirements before building the workflow.
One of the ways Jake figured out how to send information back and forth between his CRM and Maroo was by using an email parser. It’s “essentially a mailbox that you teach to recognize key points of data,” says Jake. With that in place, Jake was able to pass information about the client (names, emails, etc) and the invoice amount over to the email parser.
With that data stored in the email parser, Jake created two Zaps: one passed the client name and email into Maroo, and the other passed the invoice amount. This was his case-study configuration, so test a sample record and confirm the available actions and fields in the current connector before relying on it.
In Jake’s case study, the workflow reduced setup to a final review and sharing step. For a simpler current option, create a Payment Link in Maroo and place it in your external CRM or email template. For itemized client work, create an invoice in Maroo and share its link. In either path, review the client and amount before sending.
Maroo now supports both paths: keep lead and client work in Maroo CRM, or connect an external CRM through the integration method that fits your stack. Recheck the current integration documentation whenever a connector or third-party workflow changes.
.png)