Ninja Forms to Excel Online: Real-Time Sync, No Zapier

Yes. Ninja Forms, active on 600,000+ WordPress sites (WordPress.org, 2026), can stream every submission into an Excel Online workbook on OneDrive in real time. No Zapier, no Power Automate flows, no CSV exports. The connection runs over Microsoft Graph, Microsoft's official API for Microsoft 365.

The setup is a mirror by default: submissions deliver to Google Sheets as the primary destination, and each row is copied into your Excel workbook at no extra cost. If your organization needs Excel as the only destination, with no Google account in the loop at all, that runs as a paid add-on. Both paths are covered below.

This guide walks through connecting your Microsoft 365 account, how rows map into an Excel table, the difference between the free mirror and Excel-primary, and how destination-aware retries protect deliveries.

Three realistic routes exist: export submissions from Ninja Forms as CSV and import them into Excel by hand, build a Power Automate flow, or use a WordPress plugin that writes rows to your workbook directly through Microsoft Graph. For live lead capture, direct delivery is the least work and the least lag.

CSV export is fine for archives but hopeless for a live pipeline: the workbook is always stale, and someone owns the chore forever. Power Automate can do the job, but you build and maintain the flow yourself, behavior depends on your Microsoft 365 plan and connector availability, and debugging failed runs becomes your hobby.

Direct delivery is mapped once in WordPress and then forgotten. The comparison table on this page summarizes all three, and the deeper cost breakdown is in WordPress forms to Excel vs CSV export vs Power Automate.

The Excel connection takes one OAuth sign-in on top of a working Sheets setup, and it needs a Microsoft 365 work or school account - Microsoft's Excel API only reaches workbooks stored on OneDrive for Business or SharePoint, so consumer OneDrive cannot be used. Since the free path mirrors from a Google Sheets primary, get that base connection running first; one-click Google connect takes about a minute (or use the classic Apps Script webhook), and neither path needs Google API keys. The steps from there:

1. Set up the base Ninja Forms to Google Sheets connection, following the Ninja Forms setup guide.
2. In the plugin settings, enable the Excel Online destination and click Connect Microsoft.
3. Sign in and approve the consent screen with a Microsoft 365 work or school account. Personal Outlook.com accounts are not supported by Microsoft's Excel API.
4. Choose the workbook and worksheet that should receive submissions.
5. Submit a test entry and confirm the row appears in both the sheet and the workbook.

If you have not built the Ninja Forms side yet, the full walkthrough with screenshots is at Ninja Forms to Google Sheets step by step.

The free path is a mirror: Google Sheets is the primary destination, and every row is copied into your Excel Online workbook as well. Excel as the primary destination, meaning no Google account anywhere in the loop, is part of the AI Pack ($29/mo).

Most teams are well served by the free mirror. You get a live Excel workbook for the people who work in Microsoft, plus a Google Sheet that costs nothing to keep as a second copy of your lead data.

Excel-primary exists for organizations that cannot route data through Google at all, usually for IT policy or client-contract reasons. If that describes you, the add-on details are on the pricing page. Either way, the Ninja Forms side of the configuration is identical.

Failed deliveries enter a retry queue that is destination-aware: if OneDrive hiccups, the Excel delivery retries on its own schedule with exponential backoff, without re-sending the row that already reached Google Sheets. A delivery log records each attempt per destination, and a manual Retry Now covers anything persistent.

That per-destination bookkeeping matters once you write to two places, because the alternative is duplicate rows in one destination whenever the other fails. Serious webhook infrastructure works the same way: Hookdeck, which has processed well over 100 billion webhooks, treats delivery success below 99% as worth investigating (Hookdeck, 2025), and Svix's default policy retries failures 8 times over roughly 28 hours (Svix docs).

Not every failure deserves the same response, and the queue treats them differently. Transient trouble, like Microsoft Graph throttling a burst of writes or returning a server error during an outage, is exactly what exponential backoff exists for: wait, retry, succeed. An expired or revoked Microsoft connection is different, because no amount of retrying revives a dead token. The delivery log surfaces that case distinctly, so you know to reconnect the account rather than wait.

The log is also per destination, which turns a vague "sync is broken" report into a two-minute diagnosis: you can see at a glance whether the problem sits on the Google side, the Microsoft side, or your own server's outbound connection.

The practical result: a Microsoft outage costs you minutes of latency, not leads.

The order that works: get Ninja Forms delivering to Google Sheets first, connect your Microsoft account, pick the workbook, and send a test submission that shows up in both destinations. From there the mirror runs itself, and the destination-aware retry queue handles the bad days.

If your team turns out to live entirely in Excel, evaluate the Excel-primary add-on once the mirror has proven itself. Integration details and version notes for the Ninja Forms side are on the Ninja Forms integration page.