Node: Append Row to Google Sheets (coming soon)

Coming soon: the Append Row to Google Sheets node will export board or conversation data to a spreadsheet. In the meantime, use the HTTP node with n8n, Make or Zapier.

Jul 11, 2026

Watch this step in the video · Projects and Team

Coming soon. The Google Sheets integration is built but can't be connected in Omnifox yet; in Settings → Integrations its card shows as "Coming soon", so today this node always skips. This article describes how it will work. In the meantime you can send the data to n8n, Make or Zapier with the HTTP node (from the Impulsa plan) and let that tool append the row in Google Sheets.

Once the integration is available, the Append Row to Google Sheets node will automatically add a row to a Google Sheets spreadsheet from a workflow. It will be the simplest way to send Omnifox data (board tasks, conversation data, AI classifier results, etc.) to an external spreadsheet without writing any code.

Requirements

  • The workspace must have a connected and active Google Sheets integration (it will be set up under Settings → Integrations; today its card shows as "Coming soon"). Without it, the node skips with the message "No Google Sheets integration is connected in this workspace".

When to use it

  • Logging to a spreadsheet every time a board task moves to "Done".
  • Exporting leads captured by a WhatsApp or Webchat workflow to a sheet shared with the team.
  • Keeping an external log of workflow events (e.g. every time a deal is created).

Configuration

  • Spreadsheet ID: optional on the node if the integration already has a default spreadsheet configured; if set here, it takes priority.
  • Sheet/tab name: optional; if not set, uses the integration's default tab or "Sheet1".
  • Values: the row to append. Accepts three shapes:
    • A simple list of cells.
    • A list of {value: "..."} objects (what the visual editor builds).
    • Text separated by line breaks or by "|" (e.g. {{trigger.item_title}} | {{trigger.contact_name}} | Done). Each cell supports variables, resolved right before writing.

The form in the editor

The node now has its own form in the inspector: Spreadsheet ID (the long part of the sheet URL; empty = the integration's sheet), Tab (empty = the integration's tab) and Row cells (one cell per line or separated by |, with variables). You can leave it set up; it will work once the integration can be connected.

Example

A board workflow fires when a card moves to the "Done" group. You add Append Row to Google Sheets with Values = {{trigger.item_title}} | {{trigger.assigned_user_name}} | {{trigger.completed_at}}. Every completed task gets logged as a new row in the team's spreadsheet.

Tips

  • Try the pipe-separated text format first if you don't want to build the values list by hand — it's the fastest to write.
  • The node automatically updates the integration's last-sync timestamp, handy to confirm in the Integrations panel that it's still working.

Troubleshooting

  • "No Google Sheets integration is connected": while the integration is coming soon, the node always skips with this message. Once it's available, connect or reconnect the integration under Settings → Integrations.
  • "The row to append is empty": check that the Values field isn't empty after variables are resolved.
  • The write fails but the workflow keeps going: this node never stops the workflow on a Google API error; check the error detail in the workflow's execution history.
Was this helpful?

Related articles

Message us on WhatsApp