OpenRuna
Sign in
← Workflows

0422_Schedule_HTTP_Send_Webhook

12 nodes · schedule, gmail, hubspot, httpRequest

Engine
n8n
Nodes
12
Trigger
scheduled/triggered
Source file
0422_Schedule_HTTP_Send_Webhook.json

Workflow flow

IntegrationsScheduleGmailHubSpotHTTPIFSet
100%
TRIGGER

Every day at 9 am

Schedule

Get previously HubSpot contacts

HubSpot

if last contacted before a month

IF

Get Hubspot Contact to engagement

HTTP

if there has been only one engagement

IF

Set email keys

Set

Send outreach email

Gmail

Record engagement in HubSpot

HubSpot

8 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

0422_Schedule_HTTP_Send_Webhook is a free n8n workflow on OpenRuna — 12 nodes connecting schedule, gmail, hubspot, httpRequest. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "0422_Schedule_HTTP_Send_Webhook" chains 12 nodes to move data between schedule, gmail, hubspot, httpRequest. 12 nodes · schedule, gmail, hubspot, httpRequest Execution begins at the scheduled/triggered trigger and flows through the 12 configured nodes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 12-node flow from scratch.
  • Benchmark it against your current schedule integration to spot missing steps or redundant nodes.
  • Study how data moves from schedule to gmail before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the schedule stack.

Example output

Imported into n8n, "0422_Schedule_HTTP_Send_Webhook" exposes 12 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, gmail, hubspot, httpRequest. Open each node after import to map credentials to your own schedule and gmail 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 "0422_Schedule_HTTP_Send_Webhook" JSON into a plain-English runbook, node by node. It can flag where schedule 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 schedule, gmail, hubspot, httpRequest. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0422_Schedule_HTTP_Send_Webhook" — extract schedule IDs and secrets into environment variables without changing the 12-node structure.

Frequently asked questions

How do I import "0422_Schedule_HTTP_Send_Webhook" 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 "0422_Schedule_HTTP_Send_Webhook" use?
It uses: schedule, gmail, hubspot, httpRequest. The flow diagram above shows how each service connects across the 12 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 schedule and gmail credentials in n8n after import.
What trigger type does "0422_Schedule_HTTP_Send_Webhook" 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 "0422_Schedule_HTTP_Send_Webhook" 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 schedule, gmail, hubspot, httpRequest.

Related resources