Latenode

Seamlessly sync Slack messages to Google Tasks for your team

This template starts when Slack sends a saved-item event to a Latenode webhook. JavaScript reads the message text with the Slack API.

Put the Slack token in that JavaScript node. Google Tasks creates a task with that text as the title and the permalink in the notes. Connect Google Tasks and point Slack's saved-item events at the webhook URL.

Updated Sep 15, 2026Est. run: 6sEst. cost: $0.0004
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Turns saved Slack messages into Google Tasks
  • Starts from the webhook Slack calls
  • Reads message text with the Slack API in JavaScript
  • Creates each task with Google Tasks

How it works

1
Trigger

Receive the saved-item event

The scenario starts when Slack posts a saved-message event to the webhook.

2
Logic

Read the Slack text

JavaScript loads the message body and permalink. Put the Slack token in that JavaScript node.

3
Action

Create the Google Task

Google Tasks creates a task with the message as the title and the permalink in the notes.

Setup guide

1

Add the webhook

Add a webhook trigger. In Slack, send saved-item events (star added) to that URL.

2

Store the Slack token

Add a JavaScript node and put your Slack token there. Use it to read the saved message text and permalink.

3

Connect Google Tasks

Add a Google Tasks connection and pick the task list that should receive new tasks.

4

Map message to task

Set the task title from the Slack text and put the permalink in the notes. Skip bot events in JavaScript if they would loop.

Requirements

A Slack app that can send saved-item events to the webhook
A Slack token stored in the JavaScript node
A Google Tasks list Latenode can write to

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.