Rocketlane
PROJECT MANAGEMENT · TASKS
Projects, phases, tasks, time entries and budgets for the clients they onboard.
Connect Rocketlane with Fabriq Developer
Your user pastes their Rocketlane credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Rocketlane in practice
Rocketlane’s pagination tokens expire: a nextPageToken is valid for 15 minutes, so an agent that pauses mid-walk through a large project or task list has to start the walk again rather than resume it. Page size is capped at 100 — a larger pageSize is treated as 100 — and the Companies API returns CUSTOMER companies only, so partner companies are simply absent.
Scopes that draw scrutiny
api-key headerRocketlane authenticates with a single api-key header and defines no scopes, so one credential covers projects, tasks, time entries, invoices and resource allocations alike.Invoice and invoice-payment endpointsReading invoices, their line items and their payments exposes client billing detail through the same key used for project reads.Time-off and resource-allocation endpointsStaff availability and absence records — HR-adjacent data that a project-automation integration rarely needs but always receives.
Worth knowing
- Webhook delivery counts as successful only on 200 OK or 204 No Content, and a POST with no response within 10 seconds is treated as failed, so a slow receiver loses events.
- Rocketlane guarantees exactly one delivery per event but explicitly does not guarantee chronological order, so handlers have to be order-independent rather than idempotent alone.
- Custom fields are filtered with company.field.<custom_field_id>.operator=value, which means an integration has to resolve field ids first and cannot filter by field name.
- Every response carries X-Request-Id, and that is the identifier Rocketlane support asks for when a specific call misbehaved.
- The API version is in the path (/api/1.0/); Rocketlane promises backward-compatible changes inside a version and a version bump for anything else.
Checked against API overview (2026-09-29), Pagination (2026-09-29), Webhook delivery (2026-09-29), Get all companies (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Rocketlane behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.