Agency account managers
Send each client a status report from their own project, on a schedule.
Review Float projects, team members and scheduled hours, with controlled project active/archived updates from Datapipe.
Updated November 2026
| Task name | Start date | End date |
|---|---|---|
| 1,240 | Oct 27 | Oct 27 |
| 640 | Oct 28 | Oct 28 |
| 210 | Oct 29 | Oct 29 |
Send each client a status report from their own project, on a schedule.
See overdue and unassigned work across projects without exporting CSVs.
Get a weekly answer to "what moved, what slipped" in a sheet or in ChatGPT.
Read projects, people and allocations using your Float API access token.
Changes stay off until you allow them. Allowed changes apply to Float right away, and history keeps the values before and after.
Optional project active/archived updates stay off until enabled.
Combine Float projects, team capacity and billable allocations in one agency report.
A teammate updates a project's active status, and Float updates that project via PATCH.
Limit: History records the before and after status.
See the problem in your report, then make the fix in Datapipe instead of opening Float, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to Float.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayOpen Float Projects, select the project, click Archive, and confirm.
With DatapipeIdentify finished projects in your Float utilization report and archive them from Datapipe with owner approval.
Marks one Float project as active or archived. Scheduled allocations and budgets stay the same.
Supported fields: Project status.
| Field | Before | After |
|---|---|---|
| active | 1 | 0 |
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider permissions still apply, and automations in Float may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
An API key or token from your Float account.
Read access for reports. The change action needs edit access in Float and stays off until the owner, an admin or a project manager allows it.
Anything your connected account cannot see in Float.
Projects, team members, and scheduled resource allocations from your Float workspace.
Reporting reads projects, people, and allocations. Optional project active/archived status updates are off until allowed for this data source, and every change is recorded in history. Allocations and budgets are not altered.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Projects in your Float workspace with client ID, active status, non-billable flag, and budget hours.
Team members and contractors in your Float workspace with job title, department, type, and active status.
Scheduled resource allocations by person, project, date range, and daily hours.
22 report fields across 3 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed Float changes. They can never widen their own access.
Summarize active Float projects, allocated hours, and team capacity.
Q4 Brand Refresh has 160 budgeted hours with 128 billable hours scheduled across 4 team members.
Projects in your Float workspace with client ID, active status, non-billable flag, and budget hours.
Use this template →Team members and contractors in your Float workspace with job title, department, type, and active status.
Use this template →Scheduled resource allocations by person, project, date range, and daily hours.
Use this template →Create a project and choose Float in Data sources.
Pick where it goes. This one sends the numbers to Amazon Redshift.
Pick where it goes. Choose projects, people or allocations and a destination.
| Task name | Start date | End date | Hours per day | Billable | Project name | Budget type | Budget total |
|---|---|---|---|---|---|---|---|
| 1,240 | Oct 27 | Oct 27 | 1,240 | 1,240 | 1,240 | 1,240 | 1,240 |
| 640 | Oct 28 | Oct 28 | 640 | 640 | 640 | 640 | 640 |
| 210 | Oct 29 | Oct 29 | 210 | 210 | 210 | 210 | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Float account. Nobody else gets a Float login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Float received it, the request is marked Uncertain and is never retried automatically, so you can check Float first.
Yes. Datapipe reads the reports on this page and can make one kind of change: update project active status. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 22 report fields across 3 datasets. You pick the columns when you build the report.
Projects, team members, and scheduled resource allocations from your Float workspace. Account permissions and the records available from the provider determine which rows can be read.
One for each Float account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Float when you are ready.