Instant Google Calendar Reschedule via Hardware Trigger - n8n Workflow

• Busy professionals who need quick, physical controls to delay their entire meeting schedule.


• Users utilizing n8n to integrate desktop hardware (like Stream Deck) with cloud APIs.


• Developers seeking robust n8n templates for advanced scheduling and time management.


• Anyone looking to automate repetitive calendar management tasks using an n8n workflow.

This sophisticated n8n workflow solves the problem of needing rapid, tactile control over your daily schedule. Instead of manually editing multiple events when an unexpected delay occurs, this automation allows you to press a single button (via a Stream Deck or similar HTTP-enabled device) to automatically push all your future meetings out by 15, 30, or 60 minutes. This highly efficient n8n automation provides three parallel execution paths, each initiated by a unique webhook, demonstrating powerful flow control within a single n8n workflow structure. It is an excellent example of how the n8n node ecosystem can bridge physical controls and complex API interactions, providing unparalleled convenience and saving significant time during a busy day. This reliable n8n workflow ensures your schedule is updated instantly.

The n8n workflow is initiated by an external HTTP request, serving as the primary n8n trigger. This configuration supports three parallel execution paths, one for each desired delay (15, 30, or 60 minutes):

1. Trigger Reception: An n8n webhook node receives the request from the external device (e.g., a Stream Deck button press), immediately launching the associated flow path.


2. Event Retrieval: The flow uses a Google Calendar n8n node to retrieve all events scheduled for the remainder of the current day.


3. Rescheduling Action: A subsequent Google Calendar n8n node executes the critical update operation. Based on which n8n trigger path was activated (15 min, 30 min, or 60 min), this n8n node calculates the new start and end times for all retrieved events by accurately adding the specified delay.


4. Confirmation/Error Handling: After the rescheduling attempt is completed by the Google Calendar n8n node, the n8n workflow responds to the originating webhook. A successful operation sends a 200 status code, while any internal error (like API failure) within the Google Calendar nodes triggers a 500 status response, ensuring the external system receives clear and prompt feedback. This parallel design makes these n8n templates highly adaptable.

1. Import the n8n Workflow: Copy the provided JSON data and import it into your n8n instance using the 'New' button and the 'Import from JSON' option.


2. Credential Setup: Ensure you have valid Google Calendar credentials configured in your n8n setup. Apply these credentials to all six Google Calendar n8n node instances. The credentials must have permission to read and modify events on your target calendar.


3. Webhook Configuration: Activate the n8n workflow. The three primary Webhook n8n trigger nodes will generate three distinct public URLs (even though they share the same ID in the internal structure, they form unique endpoints). Extract these three specific URLs (for 15 min, 30 min, and 60 min delays).


4. Hardware Setup (Stream Deck): Configure three separate buttons on your Stream Deck (or any similar HTTP client device) to execute an HTTP GET request to the three distinct webhook URLs provided by the n8n trigger nodes.


5. Final Activation: Save and ensure the entire n8n workflow is activated and running.

Webhook (n8n trigger node): Functions as the initiation point for the n8n workflow, receiving an external HTTP request. Three distinct webhook nodes are utilized to define the separate 15, 30, and 60-minute delay options.
Function: Listens for external GET/POST requests.
Key Configuration: Uses a fixed Webhook ID for endpoint generation.
Google Calendar (Get Events): This n8n node queries the connected Google Calendar account to find all scheduled events from the current moment until the end of the day.
Function: Retrieves the list of calendar entries to be updated.
Key Configuration: Operation: Find/Get All; Resource: Event.
Google Calendar (Push Meetings 15/30/60 Minutes Later): This critical n8n node processes the retrieved list of events and updates their start and end times to implement the delay.
Function: Executes batch updates to shift event times.
Key Configuration: Operation: Update; Utilizes expressions (must be configured by the user) to precisely add 15, 30, or 60 minutes to the event start and end times. onError is set to continueErrorOutput for robustness.
Respond to Webhook (200/500): This n8n node concludes each flow path by sending immediate feedback to the originating request, confirming success (200) or reporting failure (500).