Node reference

Write Google Sheet for Joomla and WordPress

Write Google Sheet is a Step (action) in Cloud › Google. Appends or updates rows in a Google Sheet.

Overview

Write Google Sheet is a Step (action) in Cloud › Google. Appends or updates rows in a Google Sheet.

When the flow reaches this step, JOrchestrator executes Write Google Sheet against your linked site or an external integration, using the field values you set on General and Design. Downstream steps can read the output payload fields defined for this node.

Why use this node

Write Google Sheet is a action step in the Cloud › Google group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add Write Google Sheet to a flow:

  • Automate "Write Google Sheet" as part of a larger Joomla or WordPress workflow
  • Replace manual google work with a repeatable, logged flow step
  • Chain with triggers, logic, and messaging nodes on the same canvas

Example workflows

Common patterns on the canvas:

  1. Trigger or Webhook → upstream steps → Write Google SheetSend Email or CMS update
  2. Scheduled triggerWrite Google SheetDebug (while testing) → production action

How to set it up

Values must be a JSON 2D array. Leave Spreadsheet ID empty to create a new workbook, or paste an existing id from the Google Sheets URL. Share existing sheets with the service account email.

Good to know

With no Spreadsheet ID, a new workbook is created (optional title field; defaults to the node label). Use Sheet2!A1 ranges for specific tabs. Turn on Create worksheet if missing when writing to an existing workbook.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-specific configuration fields

System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

Property keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo
_payloadFieldsAvailable Fieldspayload-panelNo

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNoNode label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
spreadsheetIdSpreadsheet ID (optional)payload-textNoLeave empty to create a new spreadsheet
spreadsheetTitleNew spreadsheet titlepayload-textNogoogleSheetsWriteNoSpreadsheetIdDefaults to the node label when empty
rangeRange (A1 notation)payload-textNoSheet1!A1 or Sheet2!A1:C3 (defaults to Sheet1!A1 for new workbooks)
valuesValues (JSON 2D array)textareaYes[["col1","col2"],["a","b"]]
writeModeWrite modeselect (append | update; default: append)No
valueInputOptionValue input optionselect (USER_ENTERED | RAW; default: USER_ENTERED)No
createSheetIfMissingCreate worksheet if missingtoggle (default: false)No

CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as {{write_google_sheet.success}}.

Field keyTypeDescription
successbooleanWhether the operation completed successfully.
spreadsheetIdstringGoogle Sheets spreadsheet ID.
spreadsheetTitlestringText value from this node's output.
spreadsheetUrlstringText value from this node's output.
spreadsheetCreatedbooleanBoolean flag from this node's output.
rangestringA1 notation range read or written.
updatedRowsnumberNumber of spreadsheet rows updated.
updatedCellsnumberNumber of spreadsheet cells updated.
writeModestringHow values were written (append, overwrite, etc.).
sheetCreatedbooleanBoolean flag from this node's output.
createdSheetTitlestringText value from this node's output.
messagestringHuman-readable status, error, or result summary.

Validation rules

  • Values (JSON 2D array) (values) must be filled before the flow can be saved.