How to connect Mailhook and Toggl Track
Create a New Scenario to Connect Mailhook and Toggl Track
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 Mailhook, triggered by another scenario, or executed manually (for testing purposes). In most cases, Mailhook or Toggl Track will be your first step. To do this, click "Choose an app," find Mailhook or Toggl Track, and select the appropriate trigger to start the scenario.

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

Mailhook
Configure the Mailhook
Click on the Mailhook node to configure it. You can modify the Mailhook URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Toggl Track Node
Next, click the plus (+) icon on the Mailhook node, select Toggl Track from the list of available apps, and choose the action you need from the list of nodes within Toggl Track.

Mailhook
⚙

Toggl Track

Authenticate Toggl Track
Now, click the Toggl Track node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Toggl Track settings. Authentication allows you to use Toggl Track through Latenode.
Configure the Mailhook and Toggl Track 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 Mailhook and Toggl Track 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
⚙

Toggl Track
Trigger on Webhook
⚙
Mailhook
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Mailhook, Toggl Track, 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 Mailhook and Toggl Track integration works as expected. Depending on your setup, data should flow between Mailhook and Toggl Track (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Mailhook and Toggl Track
Mailhook + Toggl Track + Slack: When a new email is received via Mailhook, extract project details and start a time entry in Toggl Track. Stop the time entry when a corresponding 'completed' email is received. Finally, send a summary of the time spent on the project to a Slack channel.
Mailhook + Google Sheets + Toggl Track: When a new invoice email arrives via Mailhook, extract the billable hours. Then, update a Google Sheet with the invoice details, including the billable hours. Create a new time entry in Toggl Track with the extracted information.
Mailhook and Toggl Track integration alternatives
About Mailhook
Use Mailhook in Latenode to instantly capture incoming emails and parse their contents into usable data. Trigger workflows on specific email events, like form submissions or order confirmations. Route parsed data to other apps, databases, or AI models for advanced processing. Automate email handling without code and scale as needed.
Similar apps
Related categories

About Toggl Track
Track time in Toggl Track, then use Latenode to automatically log hours to project management tools or generate invoices. Pull Toggl Track data into reports and dashboards, or trigger notifications based on time entries. Automate billing and project tracking; build custom flows around your Toggl Track data.
Related categories
See how Latenode works
FAQ Mailhook and Toggl Track
How can I connect my Mailhook account to Toggl Track using Latenode?
To connect your Mailhook account to Toggl Track on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Mailhook and click on "Connect".
- Authenticate your Mailhook and Toggl Track accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track email campaign time in Toggl Track?
Yes, use Latenode to log time entries in Toggl Track automatically upon receiving specific emails via Mailhook. Benefit from detailed campaign time tracking and enhanced reporting.
What types of tasks can I perform by integrating Mailhook with Toggl Track?
Integrating Mailhook with Toggl Track allows you to perform various tasks, including:
- Automatically log billable hours for client email correspondence.
- Create Toggl Track projects from new Mailhook email subscriptions.
- Trigger time tracking based on email content analysis via AI.
- Pause time tracking when a Mailhook email bounces.
- Generate time tracking reports based on email communication volume.
How does Latenode handle large Mailhook email volumes?
Latenode scales to process high email volumes from Mailhook, leveraging efficient queue management and parallel processing for reliable automation.
Are there any limitations to the Mailhook and Toggl Track integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical email data prior to integration cannot trigger events.
- Complex email content parsing may require custom JavaScript code.
- Toggl Track API rate limits apply to high-frequency time tracking actions.