GitHub and Harvest automations

Ready-made scenarios where GitHub and Harvest work for you: pick one — a copy appears in your account and runs on its own.

36 scenarios

Customers from GitHub become contacts in Harvest
GitHub buyers update contacts in Harvest
Abandoned carts from GitHub into your Harvest audience
Customers from GitHub into Harvest customer lists
GitHub sales land in Harvest
New card in one Harvest becomes a task in another
A new card in one Harvest creates a task in the other
Shop customers land in your CRM
Work tasks copy into your personal Harvest
New GitHub customers go straight into your Harvest lists
New project in GitHub appears in Harvest
New issues in GitHub — tasks in Harvest
A paid order in GitHub becomes an invoice in Harvest
Tasks from one task manager, mirrored in the other
Tasks sync into your other Harvest
Tasks from one Harvest appear in the other
Personal tasks flow into the team Harvest
Move tasks from one Harvest to the one you actually use
Tasks from one Harvest mirrored in the other
Copy tasks from one Harvest to another
Tasks from one Harvest — copied into the other Harvest
New Harvest contacts — into GitHub audiences
Contacts from Harvest into GitHub audiences
Route each new order into your CRM, invoices, and mailing list
All work accounts for a new hire from one form
Win back abandoned GitHub carts by email and in CRM
An invoice to the client — from one status change
Release notes — ready the moment a version ships
A lead replies — the CRM card updates and a task lands on a rep
New-issue triage: task, notification, reply to the author, and a logged row
Client onboarding from a questionnaire: project, tasks, channel, email, CRM
Daily backup of your time tracking to a repository
Pull requests and task statuses straight from commits
Tasks from your meeting recording, straight into the tracker
Action-emails — straight onto your to-do list
Every sale — logged, a ping to you and a thank-you to the buyer