Productivity · Integration
Replicon
Add Replicon to your product for your customers, and give your AI agents governed access to it.
Replicon is time tracking with an approval chain attached, and the approval chain is what makes it more than a form. A time entry sits on a timesheet, the timesheet is submitted, then approved or rejected, and only approved time should ever reach a payroll run or an invoice. An integration that writes into an approved period, or reports on unapproved hours as though they were final, causes exactly the problem the approval exists to prevent. Objects are users, projects and tasks, time entries and timesheets, billing rates and time off. Every organisation configures its own timesheet periods and approval path, so those are per-tenant configuration rather than assumptions in your code. fastn holds the credentials per tenant and maintains the connection.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Replicon instance so time your product captures lands on the right timesheet and task.
Write time entries against a project and task, then respect a submitted or approved timesheet instead of editing over it.
Read approved time only when your product bills or reports, so unapproved hours never reach an invoice.
Follow each customer's own timesheet periods and approval path, since no two organisations run the same one.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports whose timesheets are still unsubmitted with a period about to close.
An agent enters or corrects time within scoped permissions, with the entry it changed logged.
An agent summarises approved hours by project ahead of a billing run.
Example prompt
Whose timesheets are unsubmitted for this period, and how many approved hours does this project have?
Set up Replicon in 4 steps
- 01Enable the Replicon connector in your fastn dashboard.
- 02Have each customer authorise their own Replicon instance so entries are written under their credentials.
- 03Map their projects, tasks, timesheet periods and approval states, and decide what your product does with unapproved time.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Replicon integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Replicon integration without building it. Your customers connect their own Replicon account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Replicon update is not your on-call problem.
- One integration serves your product and your agents. The same governed Replicon connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
HarvestWorks well with
Workday
QuickBooksOften used alongside
Tools the same teams tend to run next to Replicon, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceReplicon integration FAQ
How do I add a Replicon integration to my product?
Enable the Replicon connector in your fastn dashboard, then let each customer authenticate their own Replicon account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Replicon client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Replicon account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Replicon account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Replicon integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports whose timesheets are still unsubmitted with a period about to close.
Who maintains the Replicon integration?
fastn does. When Replicon changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Replicon automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Replicon can trigger your workflows in return.
Does it adapt to each team's own Replicon setup?
Yes. However a team has configured Replicon, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Replicon integration?
A common starting point: let each customer connect their own Replicon instance so time your product captures lands on the right timesheet and task. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Replicon integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Replicon does not change your per-connector cost. You can start free with 3 connected accounts.
Add Replicon to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.