At Beam, we used a headless CMS to manage the documentation for all tools, agents, and integrations. There was a need for redoing the content for these items and it was naturally a tedious task as there was a combined total of 1000+ items. Since our CMS had no readily available integrations with popular tools such as Zapier, I developed an RPA workflow to generate content and plug it back into the CMS.

I used a similar process to experiment with generating SEO-compliant content for the website. The idea was to dynamically create pages for each tool, agent, and integration, which would contain the necessary documentation for each item. The automation also took care of any creations, deletions, or upserts, and updated the website’s CMS accordingly.

Another simple process I automated was maintaining parity between Beam’s application and the features and tools we claimed were production-ready, on the website. I created a workflow that made the necessary amends on the website if an item was changed in any way.