Integration
Connect actiTIME to Code::Stats
When New Customer fires in actiTIME, your agent runs Get user in Code::Stats. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want actiTIME and Code::Stats to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What actiTIME can start in Code::Stats
When New Customer in actiTIME
then Get user in Code::Stats
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with actiTIME and Code::Stats
Triggers and actions 7 triggers · 15 actions
- New Customer
Triggers when a new customer is created.
- New Project
Triggers when a new project is created.
- New Task
Triggers when a new task is created.
- New User
Triggers when a new user is created.
- Updated Leave Time
Triggers when the user's leave time is changed.
- Updated Task
Triggers when an existing task is changed.
- Updated Time-Track
Triggers when the user's working time is changed.
- Create Customer
Creates a new customer.
- Create Project
Creates a new project.
- Create Task
Creates a new task.
- Create User
creates a user account (firstName, lastName, email, username, password required; optional middleName, active, hired, releaseDate, departmentId, timeZoneGroupId).
- Find Customer
Finds the customer by name.
- Find Project
Finds project by name
- Find Task
Finds the task by name.
- Get Time-Track
Returns one time-track record (taskId, time, comment)
- List Leave Time
Lists leave-time records (userId, date, leaveTypeId, leaveTime)
- Modify Leave Time
Modifies the leave time record by replacing the existing value with a specified one.
- Modify Leave Time (Increase Time)
Modifies the leave time record by increasing the existing value by a specified value.
- Modify Time-Track
Modifies the time-track record by replacing the existing value with a specified one (along with the time-track record comment).
- Modify Time-Track (Increase Time)
Modifies the time-track record by increasing the existing value by a specified value.
- Update Task
updates a task's name, description, status/workflowStatusId, projectId, typeOfWorkId, deadline or estimatedTime.
- Get user
Retrieve a public user's profile (total XP, new XP in last 12h, per-machine, per-language and per-date XP).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from actiTIME
actiTIME to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
actiTIME to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
actiTIME to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
actiTIME to Google SheetsGoogle Sheets
actiTIME to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
actiTIME to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Code::Stats
Questions
actiTIME and Code::Stats, answered
What can start an automation from actiTIME?
Any of actiTIME's 7 triggers in the catalog, including New Customer, New Project, New Task and New User. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Code::Stats when something happens in actiTIME?
Any of Code::Stats's 1 action, including Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Code::Stats to actiTIME?
Code::Stats has no triggers in the catalog today, so automations start in actiTIME. If you need the other direction, ask: your agent reads Code::Stats's API documentation and adds it.
Do I have to build a connector for actiTIME or Code::Stats?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.