Latenode
Github
Slack

Get Slack Notifications About New GitHub Stars (Step by Step) with Latenode

This template starts when GitHub records a new star on the repository you watch, then posts the stargazer and repo name in Slack. Connect GitHub and Slack. Point the trigger at the repo and pick the channel that should see new stars.

Updated Sep 16, 2026Est. run: 5sEst. cost: $0.0003
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

  • Posts in Slack when your GitHub repo gets a new star
  • Starts from the GitHub new-star event
  • Includes the stargazer and repository in the Slack text
  • Keeps GitHub and Slack access on those connections

How it works

1
Trigger

Watch GitHub stars

The scenario starts when someone stars the GitHub repository you choose.

2
Action

Post in Slack

Slack sends a channel message with the stargazer login and repository name.

Setup guide

1

Connect GitHub

Add a GitHub connection with access to the repository. Add a GitHub trigger for a new star and select that repo.

2

Connect Slack

Add a Slack connection with access to the channel that should get star alerts.

3

Map the Slack message

Send a public or private channel message. Map the stargazer login and repository name into the text. Star the repo once and confirm Slack shows the post.

Requirements

A GitHub repository Latenode can watch for new stars
A Slack channel Latenode can post to
GitHub and Slack connections in Latenode

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.
Contact support →

More templates

You might also like

Browse all templates →

123FormBuilder to Insightly: Create leads from form submissions

Manually copying form responses into your CRM wastes time and risks errors. This integration captures each New Submission event from 123FormBuilder and uses it to Create a Lead in Insightly, mapping the respondent's name, email, and custom fields directly into a new lead record. Marketing managers and sales teams can eliminate data entry and get leads into Insightly instantly for follow-up. By connecting 123FormBuilder's form capture with Insightly's CRM, you keep your sales pipeline fed without manual work.

8s~$0.002

Create a Pipeline deal from a new Discord channel message

Sales teams often miss leads buried in Discord conversations. This scenario captures every new message in a chosen Discord channel and creates a corresponding deal in Pipeline, using the message text as the deal description and the author's username as part of the deal name. Sales managers and business development reps can log inbound signals from team discussions directly into Pipeline CRM without manual data entry. The connection turns Discord into a lead source, so no opportunity slips through the cracks.

8s~$0.002

Create a Pipeline deal when a new HubSpot deal is added

Manually copying deal data from HubSpot to Pipeline wastes time and risks errors. This automation triggers on the New Deal event in HubSpot and then runs the Create Deal action in Pipeline, mapping the deal name, amount, and associated contact email and name. Sales operations teams and CRM administrators who use both HubSpot and Pipeline can eliminate duplicate data entry. HubSpot captures the initial deal, and Pipeline receives a matching record immediately, so both systems stay aligned without manual work.

8s~$0.002