Hi everyone,
I’d like to share a client case study—it might be of interest to other integrators. Well, actually, it’s a small agency that manages about ten content creators for various brands. They store contracts, creator profiles, and the entire signing workflow in OpenKM. Nothing out of the ordinary so far. The problem arose two months ago when they wanted their partner brands to be able to view an up-to-date profile with follower stats (Instagram, TikTok, etc.). OpenKM obviously has no way of handling external data that changes daily—it’s not designed for that. I looked into custom scripts and API connectors to social media platforms… but for just a dozen profiles, developing and maintaining all that—frankly, the cost makes no economic sense for the client. So we looked for a compromise between the existing internal workflow and an external tool, without having to start from scratch with heavy-duty code. In the end, the client opted for a separate solution to generate the media kit with up-to-date stats, and from OpenKM we simply sync the basic information (name, contract, status) via a scheduled CSV export. In short, this avoids duplicating business logic, and OpenKM remains the single source of truth for signed documents. How do you handle the synchronization frequency? Do you use a standard cron job for the export, or do you use a webhook triggered directly from the OpenKM workflow? I’m concerned that the scheduled CSV export could quickly become a bottleneck if the client grows.
I’d like to share a client case study—it might be of interest to other integrators. Well, actually, it’s a small agency that manages about ten content creators for various brands. They store contracts, creator profiles, and the entire signing workflow in OpenKM. Nothing out of the ordinary so far. The problem arose two months ago when they wanted their partner brands to be able to view an up-to-date profile with follower stats (Instagram, TikTok, etc.). OpenKM obviously has no way of handling external data that changes daily—it’s not designed for that. I looked into custom scripts and API connectors to social media platforms… but for just a dozen profiles, developing and maintaining all that—frankly, the cost makes no economic sense for the client. So we looked for a compromise between the existing internal workflow and an external tool, without having to start from scratch with heavy-duty code. In the end, the client opted for a separate solution to generate the media kit with up-to-date stats, and from OpenKM we simply sync the basic information (name, contract, status) via a scheduled CSV export. In short, this avoids duplicating business logic, and OpenKM remains the single source of truth for signed documents. How do you handle the synchronization frequency? Do you use a standard cron job for the export, or do you use a webhook triggered directly from the OpenKM workflow? I’m concerned that the scheduled CSV export could quickly become a bottleneck if the client grows.
