Runrun.it (Runrunit) is a work-management platform for planning tasks, projects, and teams. The connector extracts clients, projects, tasks, task attachments, dashboards, and users from the Runrun.it API.

Configuring Runrunit as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Runrunit option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

Connect using credentials from your Runrun.it workspace. See the API documentation for where to obtain an application key and user token. The following configurations are available:

Application Key (app_key): The application key associated with your Runrun.it workspace.
User Token (user_token): A user token for API calls. Ensure this user has access to the data you need to extract.

Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.

Tip: The stream can be found more easily by typing its name.

Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
- Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
- Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.

Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:

Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Runrunit and their corresponding fields:

clients

Clients (customers) in the workspace, including budget, time, and cost rollups.Key fields:

Field	Type	Description
`id`	Integer	Unique identifier for the client
`name`	String	Client name
`custom_field`	String	Custom field value for the client
`is_visible`	Boolean	Whether the client is visible for use
`project_ids`	Array	Identifiers of projects linked to the client
`budgeted_hours_month`, `budgeted_cost_month`	Number	Monthly budgeted hours and cost
`time_worked`, `time_pending_not_assigned`, `time_pending_queued`, `time_pending`, `time_total`	Integer	Time tracking in seconds
`time_progress`	Number	Time tracking progress ratio
`cost_worked`, `cost_pending`, `cost_total`	Number	Cost rollups
`activities_0_days_ago` through `activities_6_days_ago`, `activities`	Integer	Worked time today and over the prior six days
`project_groups`	Array	Legacy project group records
`time_pending_backlog`	Integer	Deprecated pending backlog time in seconds

projects

Projects with schedule, board stage, task counts, and financial rollups.Key fields:

Field	Type	Description
`id`	Integer	Unique identifier for the project
`name`	String	Project name
`client_id`	Integer	Associated client identifier
`is_closed`, `is_active`	Boolean	Lifecycle flags
`start_date`, `close_date`, `desired_date`, `estimated_delivery_date`	String	Schedule fields (string dates where applicable)
`project_group_id`, `project_sub_group_id`	Integer	Group and subgroup identifiers
`project_group_name`, `project_sub_group_name`	String	Denormalized group labels
`project_group_is_default`, `project_sub_group_is_default`	Boolean	Denormalized group default flags
`client_name`	String	Denormalized client name
`board_stage_id`, `board_stage_name`, `board_stage_color`	String/Integer	Current board stage
`tasks_count`, `tasks_not_assigned_count`, `tasks_queued_count`, `tasks_working_on_count`, `tasks_closed_count`, `tasks_backlog_count`	Integer	Task counts
`tasks_count_progress`	Number	Ratio of completed tasks
`task_points_sum`, `task_points_progress`, `task_points_not_assigned_sum`, etc.	Number	Task points and progress
`time_worked`, `time_pending`, `time_pending_not_assigned`, `time_pending_queued`, `time_total`	Integer	Time tracking in seconds
`time_progress`	Number	Time progress ratio
`cost_worked`, `cost_pending`, `extra_costs`, `cost_total`, `cost_progress`, `budgeted_cost`	Number	Financial rollups
`overdue`, `over_budget`	Boolean	Schedule and budget indicators
`activities_0_days_ago` through `activities_7_days_ago`, `activities`	Integer	Recent worked time in seconds
`time_pending_backlog`	Integer	Deprecated time field
`is_public`, `is_shared`, `use_new_permissions`	Boolean	Sharing and permissions
`sharing_details`	Object	Sharing details
`created_at`	String	When the project was created

tasks

Tasks including board placement, estimates, assignments, subtasks, and custom fields. The tap requests all statuses (including closed) via bypass_status_default.Key fields:

Field	Type	Description
`id`, `uid`	Integer/String	Task identifiers
`title`	String	Task title
`state`	String	Workflow state (e.g., not_assigned, working_on)
`is_closed`, `is_assigned`, `is_working_on`, `on_going`, `is_urgent`, `is_subtask`	Boolean	Workflow and status flags
`project_id`, `client_id`	Integer	Foreign keys
`user_id`	Integer/String	User who created the task
`responsible_id`, `responsible_name`	String/Integer	Primary responsible user
`created_at`	String	Creation timestamp
`board_id`, `board_name`, `board_stage_id`, `board_stage_name`, `board_stage_description`, `board_stage_position`	String/Integer	Board and stage properties
`type_id`, `type_name`, `type_color`	String/Integer	Task type details
`team_id`, `team_name`	String/Integer	Team when unassigned to a person
`queue_position`	Integer	Position on the assignee list
`workflow_id`, `task_state_id`, `task_state_name`, `task_status_id`, `task_status_name`	String/Integer	Workflow identifiers
`desired_date`, `desired_date_with_time`, `desired_start_date`, `close_date`, `start_date`	String	Dates and schedule
`estimated_start_date`, `estimated_delivery_date`, `gantt_bar_start_date`, `gantt_bar_end_date`	String	Estimate dates
`current_estimate_seconds`, `estimated_at`, `last_estimated_at`, `estimate_updated`, `estimated_delivery_date_updated`, `reestimate_count`	String/Integer	Time estimate properties
`scheduled_start_time`, `is_scheduled`	String/Boolean	Scheduled properties
`stage_depart_estimated_at`, `board_remaining_time`	String/Integer	Stage timing
`parents_max_desired_date`	String	Latest desired date among prerequisites
`time_worked`, `time_pending`, `time_total`, `current_worked_time`	Integer	Time tracking in seconds
`time_progress`	Number	Time tracking progress
`activities_0_days_ago` through `activities_7_days_ago`, `activities`	Integer	Recent activity (seconds per day)
`client_name`, `project_name`, `project_group_name`, `project_group_id`, `project_group_is_default`	String/Integer	Denormalized client & project info
`project_sub_group_name`, `project_sub_group_id`, `project_sub_group_is_default`	String/Integer	Denormalized sub-group info
`user_name`	String	Creator display name
`parent_task_id`, `parent_task_title`, `subtask_ids`, `subtasks_count`, `subtasks_closed_count`, `subtasks_count_progress`	String/Integer	Hierarchy details
`parent_ids`, `opened_parent_ids`, `child_ids`	Array	Prerequisite and dependent task identifiers
`all_subtasks_time_worked`, `all_subtasks_time_total`, `all_subtasks_time_progress`, `all_subtasks_times_updating`	Integer/Number	Time tracking for subtasks
`current_level`	Integer	Depth in the hierarchy
`repetition_rule`	Object	Object with rrule details and occurrence time
`repetition_rule_id`	Integer	Repetition rule ID
`assignments`	Array	Array of assignment objects (assignee, team, time info, priority, etc.)
`evaluation_status`, `approved`, `current_evaluator_id`	String/Boolean	Evaluation properties
`evaluator_ids`, `pending_evaluator_ids`, `approved_evaluator_ids`, `rejected_evaluator_ids`	Array	Evaluator lists
`tags_data`, `tag_list`, `tags`, `task_tags`	Array	Tags and tag data
`custom_fields`	Array	Array of custom fields
`form_id`	Integer	Related form ID
`is_shared`, `sharing_details`, `follower_ids`	Array/Boolean	Sharing and followers info
`attachments_count`, `checklist_id`, `points`, `was_reopened`, `overdue`, `priority`	Integer/Boolean	Miscellaneous fields (priority deprecated)

task_documents

Files and documents attached to tasks. This stream is loaded after tasks (one API request per task). Relate rows to tasks using replication metadata from the parent stream where present, or using attachable_id / attachable_type when the attachment targets a task.Key fields:

Field	Type	Description
`id`	Integer	Document identifier
`type`	String	Record type classification
`attachable_id`, `attachable_type`, `attachable_name`	String/Integer	Resource the document is attached to
`data_file_name`, `data_file_size`, `data_content_type`	String/Integer	Underlying data file metadata
`file_name`, `file_size`, `file_content_type`, `file_extension`	String/Integer	Display file metadata
`thumbnail_file_name`, `preview_file_name`	String	Preview assets
`uploaded_at`, `transfered`	String/Boolean	Upload time and transfer completion flag
`uploader_id`, `uploader_name`	String/Integer	Uploader identifiers
`remote_id`, `remote_icon_url`	String	Third-party storage identifiers
`is_shared`, `tags_data`, `has_approval_request`, `field_label`, `evaluations`	Various	Sharing and metadata fields

dashboards

User-owned dashboards.Key fields:

Field	Type	Description
`id`	Integer	Unique identifier for the dashboard
`name`	String	Dashboard name
`user_id`	Integer	Owner user identifier

users

Workspace users, roles, schedule, and preferences.Key fields:

Field	Type	Description
`id`	String	User identifier
`name`, `email`	String	Display name and email
`avatar_url`, `avatar_large_url`	String	Profile images
`cost_hour`	Number	Hourly cost
`created_at`	String	Account creation time
`is_master`, `is_manager`, `is_auditor`	Boolean	Role flags
`can_create_client_project_and_task_types`, `can_create_boards`	Boolean	Permissions
`budget_manager`	Boolean	May edit project extra costs
`is_eligible_to_access_reports`, `is_eligible_to_whatsapp`	Boolean	Eligibility flags
`time_zone`, `position`, `on_vacation`, `birthday`, `phone`, `gender`, `marital_status`, `in_company_since`, `language`	String/Boolean	Profile & availability properties
`is_certified`, `is_certified_expert`	Boolean	Runrun.it certification flags
`is_mensurable`	Boolean	RR Ratings participation
`team_ids`, `led_team_ids`	Array	Team membership and leadership
`demanders_count`, `partners_count`, `has_all_users_as_partners`, `has_all_users_as_demanders`	Integer/Boolean	Relationship counters
`is_blocked_on_mobile`, `bypass_block_by_time_worked`, `blocked_by_time_worked_at`	String/Boolean	Mobile & time tracking limits
`time_tracking_mode`	String	Deprecated; use enterprise setting
`shifts`	Array	Weekly schedule shifts
`preferences`	Object	User preferences
`theme`, `task_list_background_image_url`, `skip_time_adjust_on_task_assignment_deliver`	String/Boolean	Deprecated (prefer preferences object)
`password_updated_at`, `password_expired_at`	String	Security timestamps
`shift_work_time_per_week`	Integer	Scheduled work time
`alt_id`, `oid`	String	Internal identifiers

time_worked_by_project_and_user

Time worked report grouped by date, project, and user. Aggregating by user_id yields total time per user; filtering by client_id yields time per user within a specific client. Returns a fixed trailing window of approximately 7 days.Key fields:

Field	Type	Description
`date`	Date	Day of the time-worked aggregation.
`project_id`	Integer	Identifier of the project.
`project_name`	String	Name of the project.
`project_sub_group_id`	Integer	Identifier of the project subgroup.
`project_sub_group_name`	String	Name of the project subgroup.
`project_group_id`	Integer	Identifier of the project group.
`project_group_name`	String	Name of the project group.
`client_id`	Integer	Identifier of the client.
`client_name`	String	Name of the client.
`user_id`	String	Slug identifier of the user.
`user_name`	String	Display name of the user.
`automatic_time`	Integer	Automatically tracked time in seconds.
`manual_time`	Integer	Manually adjusted time in seconds (may be negative).
`time`	Integer	Total time worked in seconds (automatic + manual).

Data Model

The following diagram summarizes how streams relate for typical analysis. Join keys follow the field names exposed in each stream.

Use Cases for Data Analysis

This section outlines a simple pattern for analyzing Runrunit task load by project. Adjust schema and table names to match your catalog (for example tables under nekt_raw with your chosen prefix).

1. Open tasks by project

Business Value:

See how much work is still open per project
Prioritize projects with many unclosed tasks

SQL query

SELECT
   p.name AS project_name,
   c.name AS client_name,
   COUNT(*) FILTER (WHERE NOT t.is_closed) AS open_tasks,
   COUNT(*) FILTER (WHERE t.is_closed) AS closed_tasks
FROM
   nekt_raw.runrunit_tasks t
   LEFT JOIN nekt_raw.runrunit_projects p ON t.project_id = p.id
   LEFT JOIN nekt_raw.runrunit_clients c ON t.client_id = c.id
GROUP BY
   p.name,
   c.name
ORDER BY
   open_tasks DESC

SELECT
   p.name AS project_name,
   c.name AS client_name,
   COUNTIF(NOT t.is_closed) AS open_tasks,
   COUNTIF(t.is_closed) AS closed_tasks
FROM
   `nekt_raw.runrunit_tasks` t
   LEFT JOIN `nekt_raw.runrunit_projects` p ON t.project_id = p.id
   LEFT JOIN `nekt_raw.runrunit_clients` c ON t.client_id = c.id
GROUP BY
   1,
   2
ORDER BY
   open_tasks DESC

Implementation Notes

Sync behavior

Streams use full table replication in the tap (no replication_key), except report streams with sliding windows. Choosing INCREMENTAL vs FULL_TABLE in Nekt still controls how the platform merges updates into your catalog tables.
task_documents depends on tasks; include both streams if you need attachments.

API access

Ensure the User Token belongs to a user with permission to read clients, projects, tasks, users, and dashboards you expect in the extract.
Large workspaces can require many requests for tasks and especially task_documents; limit streams or sync frequency if needed.

Skills for agents

Download Runrunit skills file

Runrunit connector documentation as plain markdown, for use in AI agent contexts.

​Configuring Runrunit as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Data Model

​Use Cases for Data Analysis

​1. Open tasks by project

​Implementation Notes

​Sync behavior

​API access

​Skills for agents

Download Runrunit skills file

Configuring Runrunit as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Use Cases for Data Analysis

1. Open tasks by project

Implementation Notes

Sync behavior

API access

Skills for agents