The Black Sheep / TrueLine

TrueLine operates live entertainment venues, with tickets sold through Etix. The Black Sheep provides the AI-driven CRM, built on GHL, that was meant to become the central platform for customer data, communications, and reporting across those venues. The problem was the gap between the two. Every ticket buyer, every order, and every event lived in Etix with no path into the CRM. Without that data there was no unified customer record, no audience segmentation, and no foundation for the marketing automation the CRM was bought to do.

Two data pipelines from Etix into the CRM, scoped in December 2025.

The first syncs customers and orders through the Etix Order API. Each order comes in with the buyer's name, email, and phone, the event, the transaction amount, and the ticket details down to seat, section, and row. The integration creates or updates the CRM contact, deduplicating on email and phone so one person stays one profile no matter how many shows they buy, tags the contact by venue and buyer type, and attaches every transaction to their record.

The second syncs events through the Etix Public Activities API, carrying event name and description, dates, categories, performers, artist metadata including Spotify and MusicBrainz identifiers, price ranges, on-sale timelines, and image assets by URL. Orders and events are then paired on the event identifier, so the CRM holds complete profiles in both directions, with everything a given customer has attended, and everyone who attended a given event.

Both pipelines run on scheduled pulls, built in Make.com with field mapping, deduplication rules, and documentation, and structured so segmentation and automation can be layered on top later.

During testing we found something that mattered beyond this project. The Etix orders endpoint was returning data outside the organization our credentials should have had access to. We reported it to Etix with the exact call we were making. Their support confirmed the endpoint was returning more than it should, escalated it to their developers, and moved us to an organization-scoped endpoint. Catching that is part of what integration work is, reading what the API actually sends back rather than only checking that it responds.

Ticket buyers became CRM contacts with full purchase histories instead of rows locked inside a ticketing platform. Events carry their own metadata in the CRM, joined to the people who attended them, which is the raw material for segmentation by venue, genre, and spend. The engagement ran from December 2025 into early 2026, with the final stretch spent working through API credential scoping with Etix directly, on a thread where we, the client, and the vendor's technical support worked from the same facts.

Given the same problem now, we would build this as a small owned integration service in the client's name, webhook-driven where Etix supports it, with its own monitoring, retry logic, and logs, rather than scheduled scenarios inside an automation platform's account and operations budget. The pipelines we built do the job they were scoped to do. An owned service would make the data flow a piece of infrastructure the client holds outright, ready for the automation roadmap the CRM was chosen for.