How to connect Harvest and Github
Create a New Scenario to Connect Harvest and Github
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Harvest, triggered by another scenario, or executed manually (for testing purposes). In most cases, Harvest or Github will be your first step. To do this, click "Choose an app," find Harvest or Github, and select the appropriate trigger to start the scenario.

Add the Harvest Node
Select the Harvest node from the app selection panel on the right.


Harvest

Add the Github Node
Next, click the plus (+) icon on the Harvest node, select Github from the list of available apps, and choose the action you need from the list of nodes within Github.


Harvest
⚙
Github

Authenticate Github
Now, click the Github node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Github settings. Authentication allows you to use Github through Latenode.
Configure the Harvest and Github Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Harvest and Github Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Github
Trigger on Webhook
⚙

Harvest
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Harvest, Github, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Harvest and Github integration works as expected. Depending on your setup, data should flow between Harvest and Github (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Harvest and Github
Harvest + Github + Slack: When a Harvest project nears its budget, a Github issue is automatically created to track the potential overspending. A Slack notification is sent to the project team to alert them of the new issue.
Github + Harvest + Google Sheets: Track new commits to a Github repository and create corresponding time entries in Harvest to bill for the development work. The recorded time entries are then summarized in a Google Sheet for reporting.
Harvest and Github integration alternatives

About Harvest
Automate time tracking with Harvest in Latenode. Sync time entries to accounting, payroll, or project management. Create flows that auto-generate invoices or trigger alerts for budget overruns. Latenode provides the flexibility to connect Harvest data to other apps and add custom logic, avoiding manual updates and delays.
Related categories
About Github
Automate code management with Github in Latenode. Trigger workflows on commits, pull requests, or issues. Build automated CI/CD pipelines, track code changes, and sync repo data with project management tools. Scale code-related automations easily and add custom logic with JavaScript nodes.
Similar apps
Related categories
See how Latenode works
FAQ Harvest and Github
How can I connect my Harvest account to Github using Latenode?
To connect your Harvest account to Github on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Harvest and click on "Connect".
- Authenticate your Harvest and Github accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track billable hours against Github issues?
Yes, you can! Latenode enables automated time tracking from Github issues to Harvest, ensuring accurate billing. Benefit from no-code blocks, plus extend functionality with custom JavaScript.
What types of tasks can I perform by integrating Harvest with Github?
Integrating Harvest with Github allows you to perform various tasks, including:
- Automatically log time in Harvest when a Github issue is closed.
- Create Harvest projects from new Github repositories.
- Send Harvest invoices based on Github project milestones.
- Update Github issues with Harvest invoice payment status.
- Generate reports combining time tracking and code commit data.
How do I handle complex logic with Harvest and Github in Latenode?
Latenode allows you to incorporate JavaScript code, AI steps, and custom logic to tailor your Harvest and Github automations beyond simple integrations.
Are there any limitations to the Harvest and Github integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex custom field mappings in Harvest may require JavaScript transformations.
- Rate limits of the Harvest and Github APIs may impact high-volume workflows.
- Real-time synchronization depends on the polling interval configured in Latenode.