When we first built Certifier's integrations — Google Sheets, HubSpot, Salesforce, Zoom, and the rest — we used a third-party service to power them. It allowed us to deliver the first integrations to you sooner, and getting those early workflows into your hands was the right priority at the time.

But as more of you started relying on these integrations to run real credential workflows, the limitations of that approach became harder to ignore. So we rebuilt them — from scratch — on our own infrastructure. Here's exactly what that means for you.

When you connected an integration in Certifier before, you were technically connecting through a third-party service. That meant accepting its terms of service and privacy policy alongside ours — a layer of overhead you never asked for, and frankly, one we were never fully comfortable asking you to accept.

With our own infrastructure, your data flows directly between Certifier and the apps you connect. One set of terms. One company responsible.

Every integration has been rebuilt to request only the permissions it actually needs — no more, no less. Google Sheets is the clearest example of what this means in practice.

The previous Google Sheets integration requested access to your entire Google Drive — read, write, delete, everything in there. That was a technical limitation of how the integration was built, not a deliberate choice on our part. But it was not best practice, and several of you flagged it. You were right.

The new integration requests access only to the specific spreadsheet you select when setting up the automation. Nothing else in your Drive is touched. If you don't select it, we can't see it. This is how it should have always worked.

The same principle applies across all other integrations — Microsoft Excel, HubSpot, Salesforce, and others. Each one now requests only what Certifier actually needs to do its job. The specifics differ per integration, but the direction is the same: narrower scope, less exposure, more trust.

Running integrations through a third-party platform created a blind spot for our support team. When something broke in your automation, we often couldn't see what was happening on the middleman's side. That meant slower diagnosis, harder debugging, and sometimes the honest but frustrating answer that the issue was outside our control.

With our own infrastructure, we have full visibility into every part of the system. When something goes wrong, we can find it and fix it — end to end, without pointing elsewhere.

Owning the infrastructure means we control the roadmap — and we've already started moving. We're currently building our first LMS integration with Canvas LMS, with more to follow.

Beyond new integrations, this foundation is what makes more sophisticated automation capabilities possible: multi-step workflows, conditional filters, delays between steps. These are things that simply weren't feasible to build cleanly before. They are now.

We know this asks something of you. Reconnecting apps and recreating workflows isn't a two-minute job — depending on how many automations you have, it could be anywhere from 15 minutes to a couple of hours. We don't take that lightly, and we wish we could make it simpler.

What we can tell you is that we built this change for the long term — for your data security, for the reliability of your workflows, and for everything we want to build next. We think it's worth it. And we'll do everything we can to make the migration as straightforward as possible: step-by-step guides, support on hand, and a call if you need one.

The old integrations will stop working on [SUNSET DATE]. This section walks you through recreating your existing automations using the new native connectors.

The process is the same for every integration: open your old automation, note how it was configured, and recreate it using the new connector. We use Google Sheets as the example below, but the same two-tab approach works for Microsoft Excel, HubSpot, Salesforce, and every other integration.

Estimated time: 5–10 minutes per automation.

You will need:

Go to Integrations → Automations in your Certifier workspace. Find the automation you want to migrate — it will be marked with a "Migration required" label.

Open it and keep it open. You will refer back to it throughout this guide.

In a new browser tab, go to Automations → + Create Automation, select the Google Sheets template, and press Use Template.

Now you have both tabs open side by side — old on the left, new on the right.

In your old automation, click the Trigger block and open the Configuration tab. You'll see:

In your new automation, configure the Trigger the same way — same account, same spreadsheet, same worksheet.

In your old automation, click the Action block (Issue Credential) and open the Configuration tab. You'll see which Credetnial Template is selected (1) and how your spreadsheet columns are mapped to credential fields — Recipient Name (2), Recipient Email (3), and any custom attributes (4).

In your new automation, set up the Action the same way — same column mapping, same credential fields.

Once everything looks right in the new automation, press Save & Activate. Give it a clear name and confirm.

Go back to the tab with your old automation. Once the new one is active and working, open the old one, click the menu in the top right, and select Delete.

That's it. Your Google Sheets automation is now running on Certifier's own infrastructure with narrower permissions. Repeat this process for any remaining automations.

The migration flow is the same for all integrations: open the existing automation, note the trigger and action configuration, recreate it using the new native connector, then delete the old one. The specific fields will differ by integration, but the steps above apply in every case.

If you're unsure about a particular integration, reach out to support, and we'll walk you through it.

If you run into anything unexpected, contact support via chat or at [email protected]. If your setup is complex and you'd prefer to talk it through on a call, just let us know — we're happy to help.