EARLY (Timeular)
ProductivityEARLY, formerly Timeular, is the time tracking platform paired with a physical tracker. Agents start and stop live tracking, create time entries with tags and mentions, organize activities and folders, pull reports, manage team folder access, and handle leave and its approval.
What This Integration Enables
EARLY, which many teams still know by its former name Timeular, sells time tracking that does not feel like time tracking: an eight-sided tracker on the desk, flipped to a face, records against an activity. What makes the platform interesting to automate is what it holds besides the hours. Folders decide who can create activities and tags and who may only track against what somebody else created. Leave is a first-class object with its own types, requests and approvals. So EARLY knows both where the hours went and who was not there, which is a rarer combination than it sounds and makes it a genuine capacity system rather than a stopwatch.
FlowRunner agents drive the live tracker, file and correct time entries, keep activities and folders organized, generate reports, manage folder access, and handle leave including its approval. Two of EARLY's own behaviors shape every flow built here. Writing time never fails for overlap: EARLY's own documentation says an entry will be created even if it overlaps others, and existing entries are split or deleted so the new one fits. And a note's tags and mentions live inside the note text as delimited references rather than as a separate list, so writing a hash tag by hand produces a note that looks right and is linked to nothing. The connector takes plain tag and mention lists and builds the delimiters, which is the difference between a tag report that works and one that stays silently empty. Where a write reaches a colleague rather than a number, FlowRunner's human-in-the-loop design puts a person in the path.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Approved absence reaches the place capacity is measured
Leave is approved once, in the HR system where it belongs, perhaps BambooHR or a Workday-shaped process. The agent picks it up, resolves the person and the leave type with List Leave Types, and checks List Leaves so the same absence is not booked twice. The proposal goes to the manager for confirmation. On approval, Create Leave For User writes it, and the week's report from Generate Report reads as a short week rather than as an underperforming one. EARLY expands leave longer than that day's working hours into a full day rather than trimming it, so the booking is worth being precise about.
-
The tracker is running, so the rest of the stack knows
Get Current Tracking answers what is running right now. A flow can use it to keep a status line in Slack honest, or to catch a tracker left running overnight and post a reminder rather than silently ending it. When time genuinely needs to be filed from elsewhere, the agent uses Create Time Entry, and it reads Find Time Entries for the range first, because EARLY will make room for the new entry by splitting or deleting what was already there. Cleanup gets the same care: Delete Tag and Delete Mention answer with the time entries they edited and whether they had to touch the running tracking, so a tag tidy-up can log exactly what it changed.
-
A folder for the client, retired without losing the history
When an engagement starts, the agent creates a folder for it, adds the activities the team will track against, and calls Add Folder Member for each person, which takes an email address rather than an id. Somebody with a seat joins immediately; anyone else is invited and comes back marked pending. When the engagement ends, the flow archives rather than deletes. Archive Folder takes its activities, tags and mentions with it and Unarchive Folder brings them all back, while Delete Folder is permanent and EARLY says it cannot be undone. The time already tracked survives either way, which is exactly why the reversible route is the default and the permanent one is an explicit answer to an explicit question.
Human-in-Loop Highlight
Create Leave For User is the operation on this connector that acts on a person rather than on a record. It books absence on a team member's behalf, already approved, without their acceptance, and EARLY restricts it to admins and owners for that reason. An agent syncing from an HR system will get it right most of the time and will be spectacularly wrong the rest, because a canceled request, a half-day, or a range typed with the wrong year all look like ordinary input. So the agent stops with the specifics on the table: "HR shows M. Lindqvist approved for Vacation, 12 to 16 October, five working days. EARLY currently holds nothing for that range. Book it as approved, book it as a request they confirm, or skip?" The manager answers. Deny Leave can reverse a future booking whatever its status, but past leave can only be acted on while it is still pending, so a mistake that ages becomes a conversation rather than a correction. That asymmetry is the reason the pause sits before the write and not after it.
Agent Capabilities
49 actionsAccount
3- Get Current User Returns the person the credentials resolve to. The quickest confirmation that a connection works.
- List Users Lists the account's users, which is how a flow resolves who a folder membership or a leave booking concerns.
- Fetch API Key Returns the API key currently in use, read only. Generating a new pair would invalidate the one this connection holds, so the connector deliberately does not offer that.
Folders
7- List Folders Lists the folders that group activities, tags and mentions.
- Get Folder Returns one folder with its settings.
- Create Folder Creates a folder, which is the unit that decides who can see and create what.
- Update Folder Changes a folder's details.
- Archive Folder Archives a folder along with its activities, tags and mentions. The reversible way to retire an engagement.
- Unarchive Folder Brings an archived folder back with everything that went with it.
- Delete Folder Permanently removes a folder. EARLY takes a few minutes over it and says it cannot be undone.
Folder Members
4- List Folder Members Lists who has access to a folder and at which level. Full members can create and edit the folder's activities and tags; personal members can only track using them.
- Get Folder Member Returns one folder membership.
- Add Folder Member Grants access to a folder by email address rather than by id. Somebody with a seat joins immediately; anyone else is invited and comes back marked pending.
- Remove Folder Member Withdraws access. Removal takes a few minutes and the person afterwards appears among retired members rather than disappearing.
Activities
5- List Activities Lists the activities time can be tracked against.
- Create Activity Creates an activity in a folder.
- Update Activity Changes an activity's name, color or folder.
- Archive Activity Archives an activity. The time already tracked against it survives.
- Unarchive Activity Brings an archived activity back into use.
Live Tracking
5- Get Current Tracking Returns what is running right now, or nothing if the tracker is idle.
- Start Tracking Starts tracking an activity. Starting while another tracking runs is refused rather than queued, because EARLY runs one at a time.
- Edit Tracking Changes the activity, start time or note of a tracking that is already running.
- Stop Tracking Ends the tracking and keeps the time as an entry. Like any write here, it makes room for itself by splitting or deleting entries it overlaps.
- Cancel Tracking Abandons the tracking and creates no time entry at all. The distinction from Stop Tracking is the whole point of the pair.
Time Entries
5- Find Time Entries Returns entries over a range. The read to run before any import, so a flow knows what it is about to overwrite.
- Get Time Entry Returns one entry with its activity, note, tags and mentions.
- Create Time Entry Files time. EARLY requires at least one minute and rejects the trailing timezone marker a standard timestamp carries, both of which the connector handles.
- Update Time Entry Corrects an existing entry.
- Delete Time Entry Removes an entry.
Tags and Mentions
7- List Tags And Mentions Lists the tags and mentions available in the account, with the ids the note references are built from.
- Create Tag Creates a tag in a folder.
- Update Tag Changes a tag's label or scope, which changes it everywhere it appears in note text.
- Delete Tag Removes a tag and answers with the time entries it edited and whether it had to change the running tracking, so a cleanup can log its own blast radius.
- Create Mention Creates a mention, which is EARLY's way of naming a person or client inside a note.
- Update Mention Changes a mention.
- Delete Mention Removes a mention, reporting the entries it touched the same way tag deletion does.
Reports
1- Generate Report Builds a report over a range. JSON works on any plan while the spreadsheet formats need a paid subscription, and an entry straddling the range boundary is counted only for the part inside it.
Leave
7- List Leaves Lists leave over a range, which is the read that explains a short week before anybody asks about it.
- List Leave Types Lists the kinds of leave the account defines, which is what a booking has to resolve against.
- Create Leave Requests leave for the connected user.
- Create Leave For User Books leave on a team member's behalf, already approved and without their acceptance. Restricted by EARLY to admins and owners, and the operation this page's human gate exists for.
- Approve Leave Approves a leave request. Future leave can be acted on whatever its current status; past leave only while it is still pending.
- Deny Leave Denies a leave request, and for future leave this is the reversible way to undo an approval.
- Delete Leave Removes a leave record outright. Denying is usually the call that leaves a trail.
Webhooks
5- List Available Events Lists the eighteen events EARLY publishes, across time entries, tracking, activities, folders and leave.
- List Webhook Subscriptions Lists what is currently subscribed, which is how a flow audits what is calling out.
- Subscribe To Event Registers a subscription for one event, for delivering somewhere other than FlowRunner.
- Unsubscribe From Event Removes one subscription.
- Unsubscribe From All Events Removes every subscription on the account, including the ones behind running FlowRunner triggers, which then go quiet until they are re-enabled.
Triggers
1 triggersEvent Triggers
1- On EARLY Event Fires on an EARLY webhook, for one chosen event or for all eighteen across time entries, tracking, activities, folders and leave. EARLY subscribes one event per webhook and offers no wildcard, so selecting all events registers eighteen subscriptions against the same callback URL, and changing the trigger's event removes the ones no longer wanted. EARLY signs nothing, so a delivery carries no signature and no shared secret: the trigger id in the callback URL routes a delivery, it does not authenticate one, and the payload should be treated as unauthenticated input by whatever the flow does next.
Frequently Asked Questions
What can FlowRunner do with EARLY (Timeular)?
FlowRunner agents can run Get Current User, List Users, and Fetch API Key in EARLY (Timeular), plus 46 more actions.
Does connecting EARLY (Timeular) to FlowRunner require OAuth?
No. EARLY (Timeular) connects to FlowRunner with session-based authentication, no OAuth flow required.
Can EARLY (Timeular) trigger a FlowRunner workflow automatically?
Yes. EARLY (Timeular) supports 1 trigger that can start a FlowRunner workflow automatically.
Other Productivity integrations
Start building with EARLY (Timeular)
Free plan, no card required. Connect in minutes.