OpenRuna
Sign in
← Workflows

0655_Code_Postgres_Update_Scheduled

23 nodes · httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
0655_Code_Postgres_Update_Scheduled.json

Workflow flow

IntegrationsHTTPSplitInBatchesPostgreSQLHubSpotScheduleGoogle SheetsMergeCodeIFSet
100%
TRIGGER

Schedule Trigger

Schedule

SET SMARTLEAD API KEY

Set

FETCH ALL CAMPAIGNS

HTTP

SEARCH

PostgreSQL

Postgres

PostgreSQL

Google Sheets

Google Sheets

HubSpot

HubSpot

If

IF

Loop Over Items

SplitInBatches

Code

Code

HUBSPOT TABLE

PostgreSQL

Postgres1

PostgreSQL

EXTRACT CAMPAIGN DATA

HTTP

UPDATE CAMPAIGN

PostgreSQL

Merge

Merge

Loop Over Items1

SplitInBatches

UPSERT CAMPAIGN ACTIVITY

PostgreSQL

UPDATE HUBSPOT ACTIVITY TABLE

PostgreSQL

18 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

0655_Code_Postgres_Update_Scheduled is a free n8n workflow on OpenRuna — 23 nodes connecting httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "0655_Code_Postgres_Update_Scheduled" chains 23 nodes to move data between httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets. 23 nodes · httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets It starts from a scheduled/triggered trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Study how data moves from httpRequest to splitInBatches before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the httpRequest stack.
  • Import "0655_Code_Postgres_Update_Scheduled" into n8n, reconnect credentials for httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets, and run the same automation in your own workspace.
  • Use it as a starting template when wiring httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "0655_Code_Postgres_Update_Scheduled" exposes 23 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets. Open each node after import to map credentials to your own httpRequest and splitInBatches accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "0655_Code_Postgres_Update_Scheduled" JSON into a plain-English runbook, node by node. It can flag where httpRequest rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0655_Code_Postgres_Update_Scheduled" — extract httpRequest IDs and secrets into environment variables without changing the 23-node structure.

Frequently asked questions

How do I import "0655_Code_Postgres_Update_Scheduled" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "0655_Code_Postgres_Update_Scheduled" use?
It uses: httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets. The flow diagram above shows how each service connects across the 23 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own httpRequest and splitInBatches credentials in n8n after import.
What trigger type does "0655_Code_Postgres_Update_Scheduled" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "0655_Code_Postgres_Update_Scheduled" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for httpRequest, splitInBatches, postgres, hubspot, schedule, googleSheets.

Related resources