Connect Rework's v3 apps - BPM, Project, Field, Prospectors, Lead, Sales, Dataset, Success, Academy, Workflow, Commerce, Inventory, Form, Booking, Workforce, Mail, Chat, Office and Task - to your AI. Add the platform connector for a whole set of apps at once, or a single app - pick below. One Rework sign-in covers them all.
https://aiconnector.rework.com/v3/mcpWorks in Claude, ChatGPT and any AI that supports remote MCP connectors: add a custom connector, paste an app's URL, sign in with Rework.
Pick your assistant - the steps differ slightly, the URL is the same either way. One Rework sign-in covers every v3 app.
Custom connectors need a paid ChatGPT plan (Plus, Pro, Business, Enterprise or Edu) - they aren't available on Free. On Business / Enterprise, a workspace admin creates the connector and publishes it to the workspace instead.
Using a different assistant? Anything that supports remote MCP connectors works the same way - paste the URL, sign in with Rework.
Each connector you add keeps its own sign-in, so connecting another Rework connector - another app, or another account - never signs this one out. If a connector ever says its sign-in was replaced, Disconnect and Connect it once.
Pick a single app or a platform bundle. Using several apps? Put them in one connector - a platform bundle or Everything - rather than adding each app on its own: one connector, one sign-in. What the connector covers and its tool list update with your choice.
More v3 apps appear here as they reach production - each at its own /v3/<app>/mcp.
Every v3 connector also carries rework_feedback_submit: tell your AI what's missing or confusing and it sends a feature request or issue straight to the Rework team.
List the services you can act on (with your create / manage rights) and read a flow's full graph - blocks & routing - in one call.
Start a job, watch its live per-stage state, update its fields, and advance the waiting stage - submit Manual forms, approve / reject Approvals, confirm or retry a paused AI step.
Post notes & threaded replies in a job's discussion; keep a checklist (todos with assignee + deadline) on any stage.
One tool edits the whole flow: rename the service, add / edit / delete blocks, wire the routing, then validate the graph (one Start → … → End).
Run a service as a portfolio of projects - one per client or initiative. Give each project as many task boards as it needs plus an issue tracker, and read a whole project page in one call.
Create & assign tasks, move them through your item stages, group them into time-boxed roadmap phases, and watch each phase roll up its own progress, workload & cost.
Shape the service once - item stages, project stages, item types & rates - then track milestones, outcomes, a ranked backlog and weekly check-ins.
Book workload (time), cost and income per project, so each one shows real revenue, cost & profit - not just effort - with reports & dashboards on top.
Run field-service jobs for your customers - each job breaks into appointments your crew executes: dispatch, assign, check in on site, check out when done, with no-show and reschedule handled cleanly - and crew members can propose a slot for a manager to approve.
Put a rep on a route: one plan = staff + customer accounts + recurrence (say, every Tue & Thu). The plan computes the schedule of visits; checking in on an occurrence creates the visit - with per-account route notes.
See what needs action now - jobs with no appointments and unassigned slots - plan the week's board, and track work shifts (a check-in always happens on shift).
Customers come straight from your Sales app. Read visit history per account, customer feedback with ratings & tags, comments on any job or visit, and FSM / visit-coverage reports.
Decide what each service collects - on every visit for a visit-planning service, on every job for a field-service one. Add a field for one service or reuse a shared one, then fill values by name on visits, jobs and appointment work forms.
Read across every channel - WhatsApp, Telegram, Instagram and more - in one place: services, the channels connected to each, and the conversations flowing in with their sidebar counts.
Open a conversation and page through its messages, pull the attached files & links, and look up the contact (profile) behind it with their labels & custom fields.
See the labels, teams, message templates, canned responses, custom fields and broadcasts that shape how the inbox runs.
Build "flows" - a trigger (new conversation, keyword, button, ...) plus a node graph that can send, assign, branch, wait or hand off to an AI agent - then save, publish, pause or run them.
Run your lead funnels - capture a lead, fill its custom fields, then move it through the stages and statuses as it qualifies. Read a lead with its full history, activity and associations; list & count leads with filters. Keep its story in one place: add notes and log calls and meetings on the lead.
Track campaigns end to end - ad, email or router - with spend, budget & UTM, brief, goals and team, plus per-campaign analytics so you see which campaign drove which leads.
Route incoming gateway events into the right funnel, connect sources & channels, and keep a clean contact profile per person - de-duplicated, with their timeline across every funnel.
Read cross-funnel insights - counts, trends and activity across services - and build an audience from your leads to push to an ad provider for retargeting or look-alikes.
Decide who gets each lead and how fast they must act: round-robin, weighted or lead-pool teams, rules by source, country or tier, response-time SLAs that remind or reassign, and automatic conversion to a Sales deal when a lead qualifies - plus how each SLA is doing.
Describe a follow-up plan and your AI builds the sequence: automatic emails and chats plus calls, LinkedIn touches and to-dos for your reps, each on its day. Write the emails in the same request - their templates are created for you. Chat steps are added as placeholders for you to finish in the app, then publish. Then enroll leads - by name or email address - after a preview of who goes in, who sends and when.
Run your deal pipelines end to end - open a deal, fill its custom fields, move it between stages, then close it won or lost with a reason. See a pipeline as a board with per-stage totals, or page through the whole table with filters.
Keep your account and contact directories current - create and edit companies and the people at them, set owners and collaborators, and read any party with their whole deal history attached.
Build the commercial detail on a deal: product line items with price, quantity and discount, the extra people on the buying committee, and orders, contracts or subscriptions with their own status. Quotes are built in Commerce.
Commit deals to a monthly forecast against quotas and read the gap, aggregate any slice of the CRM into numbers, and find and merge duplicate deals, companies or people.
Build your own tables for anything you track and keep them in folders. Pick the columns from your shared field library - text, numbers, dates, pickers, people, links to other tables - and set each column's width, visibility and whether it's required.
Add, edit and reorder rows and fill every cell, share a row with teammates, and read its change history. Linked columns pull the related rows - and the values looked up or rolled up from them - straight in.
Create or update up to 100 rows at once, duplicate rows, search across every table, folder and row, and filter, sort and page through large tables.
Save views - a named filter, sort and layout - and pick the default. Group and summarize rows (count, sum, average, min, max) on tables with analytics turned on, without exporting anything.
Draft and edit Help Center articles - title, summary, body and tags - and keep them as drafts until they're ready. Headings, lists and images in the body show up in the Help Center as written. Retire old articles by archiving them.
Upload an image from a file or a link and place it in an article, with its size, alignment and caption set right in the text.
Sort articles into categories (they can nest), then publish them onto the collections of your public Help Center site - several articles at once.
Keep a glossary of terms - each with its definition, alternative spellings and related terms - shown across your Help Center.
Write the API documentation on your developer site: guide pages (getting started, authentication, how-tos with code samples and tables) and a page for each API endpoint - its parameters, request body, responses and sign-in. New pages start as drafts.
See the whole table of contents as readers get it - and what is still a draft - then nest and reorder sections and move pages between them in one go. Your AI warns you about a page readers can't reach.
Give your AI an OpenAPI file (JSON or YAML, or a link to it). It shows which endpoint pages would be added or changed - nothing is written until you say go. Pages no longer in the file are listed, never removed.
Create a course in one of your training programs - title, subtitle, description, length, what learners will learn, what they need first and who it is for, plus a cover image. Every new course starts as a draft.
Add sections and lessons in order - text pages with headings, lists, tables and images, links to videos (YouTube, Vimeo and others) and reflection pages - then rename or move them as the course takes shape. A whole outline can be built in one go.
Add quiz lessons and fill them with questions - multiple choice (one or several right answers) or written answers - each with an explanation. Set the pass mark, retries and the messages learners see. Add a final exam or a practice exam to the course.
Your AI never publishes and never removes anything: edits keep every lesson and question already there. Review the draft in Academy and publish it when it's ready.
Browse your workflows (pipeline templates) and the ordered stages a job passes through; stand up a new workflow or add stages, and set branching rules - "if the amount is over 5,000, go to Manager approval".
Create a job and drive it through the pipeline - advance, send back, fail, reassign, move or archive - filling the stage form and custom fields as you go.
Your personal task inbox and a dashboard of active / overdue jobs and open todos; keep a checklist on any job.
Recurring schedules that spawn jobs, labels & tags, end-reasons for when a job finishes or fails, and the compose form.
"Set up a 30-minute project sync with An and Binh on Friday at 10" - your AI creates the meeting with its time, people, agenda, location or video link, and can reserve a room for it.
Move a meeting (it keeps its length), invite more people, update the agenda, cancel or reopen it, mark it done - and answer the invitation for yourself or remind someone.
A weekly 1:1, a review every other Friday, a meeting on the first Tuesday of each month - set it up once and each meeting is created for you. Pause, change or stop it any time.
Read the minutes, votes, action items, files, recordings and full transcripts, and search across your meetings. Write a note into a meeting - minutes, a decision, or a private note only you see - and edit it later.
Browse your catalogs and the category tree inside each; add categories and labels to keep products organised.
Find a product by name, code or SKU; create and edit products with their own price - one-off or a monthly / yearly subscription - and add variants (size, colour, plan) each priced on its own.
See which price books you sell from, their currency and validity, and which ones apply to a given customer.
Put products into a price book and set what they sell at; add volume tiers or discounts by quantity, and check the price for any quantity before you quote.
Build a quote in one request - name the products, quantities and discounts and the prices come from your price book. Add your own lines and section headings, then copy it for many customers at once.
Set up each legal entity you sell from - name, tax id, address, country, currency - and give it its own quote, invoice and payment services: the default company, document numbering, validity, payment terms and the bank account customers pay into.
Set up the discounts, tax rates and fees your quotes pick from - a percent or fixed amount, when and where a discount applies, VAT added on top or included in the price, a shipping fee or a card surcharge. Your AI shows each change before it saves it.
Set up warehouses and their storage locations - zones, racks, shelves and bins - in one go, and see what is stored where on the bin map.
On hand, reserved and available for every item - per bin and lot, and across all warehouses - with its cost and full movement history.
Receive from a supplier, ship to a customer, transfer between warehouses and count stock: your AI creates the document with its lines and posts it, and stock updates the moment it is posted.
Low-stock alerts and what to reorder, stock value by warehouse or product, and the cost of goods delivered.
Describe the form and your AI creates it with every question - text, email, phone, numbers, dates, dropdowns, ratings - laid out in sections, side by side, and across pages.
Show a question only when an earlier answer matches, fill one from the link (campaign, source) or copy another answer, and set limits like min / max or a maximum length.
Rules on the answers decide who gets emailed, which webhook receives the response, and whether people see a thank-you message or go to a page of yours.
Pick a theme, publish, and get the public link - pre-filled if you like. Then read the responses, mark spam or processed, and get a per-question summary.
See what is waiting on you, what you sent and what you approve - filter by request type, status, deadline or date, and search by words or request number.
Each request type has its own form and approval route. Your AI prepares the request with that type's fields, choices and rules, fills in tables row by row, attaches files from a link, shows the totals the form calculates, asks you only for what is missing, and files it once you confirm - or keeps it as a draft.
Open a request with every approval step and note, then approve, reject, forward it or send it back to the creator - with the fields the request type asks approvers to fill.
Comment, follow, bookmark, resend a returned request, duplicate one, and set up requests that file themselves every week or month.
Admins describe a new request type and your AI builds it: the form (fields, choices, what's required, formulas such as a Total Claim, tables of line items, file fields), the approval route - fixed approvers, approvers by department or position (the head of Finance, whoever holds CFO), steps where the filer tags someone, managers, and rules like "above 100,000,000 the CEO approves" - who can see and file it, and request numbering.
Describe the event and your AI creates it as a draft: name, description, dates in the event's own timezone, venue or an online meeting link, capacity, registration window and a cover image.
Move the date, rename it, change the city - only what you mention changes, the rest of the event stays as it is. Duplicate an event to a new date with its tickets and agenda.
Free or paid tickets with quantities and sales dates, agenda sessions with tracks and rooms, and speakers and sponsors from your library.
Who registered, who is waiting for approval, who has arrived, orders and the waitlist - with the headline numbers first. Add guests one by one or load a list, and check people in at the door.
"How many deals did each owner win this quarter?" - your AI counts, sums or averages across Sales, Lead or Request, grouped by stage, owner, source or one of your custom fields, by day, week, month or quarter - without saving anything.
Turn any answer into a chart - bar, line, pie, funnel, table and more - on a new or existing dashboard; each chart keeps its own filters. Rename, reorder and copy charts and dashboards.
A new dashboard starts with just you. Share it with the people who should see it, or co-edit it, when it's ready - they get a notification.
Save a view on a pipeline or lead board - filters, sort and columns - for yourself or the whole team, and choose how a deal or lead page is laid out (managers).
Ask what was posted this week and your AI reads the company feed - announcements, letters, news, events and polls - or one channel, one person's posts, or your saved ones, and can search all of it.
Have your AI draft a letter, a news article or a foundation post. It stays a draft only you can see until you say publish - then pick the channels, or schedule it for later.
Post an update or an announcement to a channel, comment and react, answer a poll, RSVP to an event, and approve posts waiting in channels you manage.
Create company events and invite people, run polls, see who is coming, and find, join or manage channels.
Tell your AI what should happen - "when a new lead arrives, notify its owner" - and it builds the automation: the trigger, the conditions and the steps across your apps, saved as a draft and checked before anything runs.
Your AI test-runs the draft with sample data and shows every step's result and any error. Steps that send messages or change data are listed first and only run if you say yes.
Your AI builds and tests drafts. When you're happy, open the automation in the Automation app and publish it there; pause or switch it on there too. Changes to a live automation stay in its draft until you publish again.
See your automations, which are live or paused, when the scheduled ones run next, recent runs and failures - and exactly which step failed and why.
Ask for a time and your AI checks every room (or car, or device) in the group at once - which are free, which are taken and by what, and which need a gap before the next booking or can't be booked that long.
"Book the Saigon room tomorrow 9-10 for the weekly meeting" - your AI books it, fills in the booking form, and says plainly if the slot is taken and what's free instead.
Move a booking to another time or room, cancel it to free the slot, check in, extend a meeting that runs over, or finish early and release the rest.
See a day or a week across all rooms, your own upcoming bookings or one room's schedule - and set up the rooms and devices: gap between bookings, longest booking, check-in, who may book.
One question shows every document where it's your turn - to review, approve or annotate - plus number requests to decide, your tasks and documents waiting for your signature, with what is overdue.
Open any document and see its stage, who holds it, which reviews and approvals are still open and whose they are, and what comes next - with its history, tasks and comments.
Approve or review with a note, return a document with a reason (that's how you reject), move it on to the next stage, draft a reply to an incoming document, comment, and hand out tasks from it.
Log what arrived, register it and route it to the desk that handles it; request an official number from a register. Routing and numbers can't be taken back, so your AI shows you exactly what will happen first.
Search by title, number or the text of attached files, see the register book and statistics per desk, file records into digital catalogs, and get an AI summary of a scanned document.
See and build the org chart - add, rename or move units, set a unit's head and members - and look anyone up: their title, the position they hold and their teams.
Set each person's managers (first, second, third) and peers - the people approvals and reviews go to - one at a time or for hundreds of people in one go.
Load the job catalogue, the org chart, hundreds of positions with their reporting lines and the people who hold them, in a few bulk steps - with a result for every row.
Open a new position, edit it, assign someone, hand the seat to someone else or end it - every change is kept as history.
Plan who to hire: add plan items by role, team and period with their cost, approve them (with a warning when a budget is exceeded) and turn them into real open positions.
Log outputs (deals won, revenue, reports delivered) and hours, read them by team or period, and check in KPI values each month or quarter.
Create the workspace, offices and employee types, the pay policies (personal income tax brackets, social insurance rates, benefits) and the salary components - the groundwork every employee record uses.
Hand your AI the staff list: it maps it to the import template, checks every row before anything is saved, then loads employees and their legal, family, education and work details, contracts, policies and leaves - with a result for every row.
Look anyone up and see their full profile - work info, personal and legal details, the positions they hold, their contract. Add a new hire, update details, move people between offices in one go.
Set an employee's salary, insurance base, salary components and tax / insurance / benefit policies, and their payroll bank account - for people allowed to see salaries.
Create contract types with automatic contract numbers and probation rules, write each employee's contract, mark it signed or current, and send it for e-signature after you have seen what goes out.
See and set up the termination, leave, document and change-request types your HR team works with, and the reasons for leaving.
Create a pipeline for each kind of hiring with its stages in order - applied, screening, interviews, offer, hired, rejected - plus the labels, reject reasons and candidate sources your team uses.
Write an opening - title, job code, job type, description, salary range, deadline - as a draft, review it, and publish it to the career site only after you have seen what goes live. Close it when the role is filled.
Add candidates to an opening (with a heads-up when the same person applied before), move them through the stages, reject with a reason and leave notes for the team.
The funnel per stage, which sources bring candidates who get hired, time to hire and each recruiter's activity - for a pipeline, an opening or a date range.
Start from the default steps and shape them: what the new hire fills in, reads and signs, a training quiz, tasks for the team and IT setup, introductions, the day-one schedule and a pulse survey - in the order you want.
Fill steps from ready-made templates, and set the invitation, welcome and team announcement emails each new hire triggers - nothing is sent while you edit.
Shift types and blocks, working areas, holidays and timesheet symbols; check-in channels and personal codes; a schedule with its working pattern (or a ready-made template) and a timesheet with its pay rules; then enrol your people.
Generate a month from the pattern, add or copy shifts, assign people, fill open shifts, and publish after you have seen what goes out - with a check of what is still missing first.
Read each person's day and fix a missed punch with a reason, work through check-in requests and shift swaps. Location, device and selfie details are never shown to your AI.
Set overtime policies, purposes and templates; file requests; approve, reject or confirm them one by one or in batches; see hours against the limits.
Open a period, see what blocks it, move it to Review, correct day values, send people their timesheets and export them. The final lock stays in the app, because that is where pay is computed.
Start from a pay rule set, see a timesheet's rules and their history, change them, or copy them to other timesheets - after a preview.
Say what you need: your AI picks the leave type, shows the days it costs and your balance after, flags anything in the way, and files it once you agree. Part of a day works too.
See every leave type you can use, what is left, your past and pending requests - and cancel one that is still waiting.
See what is waiting on you, open a request with its days and balance, approve or reject with a note, one by one or in bulk.
Create leave policies, try the rules before saving, enrol people, and load opening balances in bulk with a check that saves nothing first. Read usage, liability and expiring balances.
Give your AI a list of customers and what to say: it writes a personal email for each one - their name, their details, no leftover {{placeholders}} - as drafts you can see in Mail.
Sending always shows a preview first and only goes out after you confirm; drafts appear in Mail before anything is sent - and only from your own mailbox.
Schedule for a time that suits each person, then reschedule, send now, or cancel back to a draft from the outbox. Failed mail can be retried.
Read threads, draft replies, find contacts and templates, mark read, star, archive, and file a conversation on a Sales deal.
Describe the email and your AI saves it as a template - or edits one you have - with merge fields like the recipient's first name, your name or the deal name, ready for anyone you share it with.
Ask what you missed: the mentions, replies to your messages and DMs waiting for you, newest first, each with its room.
Read a channel, a DM or a thread, jump to the messages around one, and search a room and the files shared in it.
Every message, edit and forward shows a preview first - the room, the exact text and who will be notified - and is sent only after you say yes. It starts with a bold line via Jolie AI (your first name), so readers know at a glance an AI assistant helped send it.
Create a channel or sub-channel and add people (also after a preview), rename a room, and choose how you get notified.
"How is the sales team doing this quarter?" - every goal's progress and pace, a line per person, per board, and what needs attention: goals behind pace and goals nobody has checked in on for a week.
"We signed 10 contracts, confidence high" - your AI records the check-in: the key result's new value, your confidence and a note. The goal's progress follows, exactly as in the app.
Create an OKR with its key results and targets - or a KPI - for a quarter, a month or the year, give it an owner, a board and labels, and activate it when it is ready.
Record a KPI metric's value for the month or quarter, and see the company and department targets your team's goals contribute to.
"Give Lan the price-list update, due Friday, high priority" - your AI creates the task with its deadline, a checklist, sub-tasks and a team queue's form fields. Every task gets a short code like MKT-42 to find it again.
What's on you, what you handed out and what you follow - plus the to-dos other apps put on you (Sales action plans, Workflow stages, approvals ...) in one list.
Start, park or finish a task with a reason; ask the person who handed it out to review it, and they accept it or send it back with a note. Comments with @mentions keep everyone in the loop.
See a plan's objectives and key results with progress from the linked tasks, post a check-in with its health, record the latest key-result value, and link tasks to a goal.
service_id is a SUID string (e.g. aExd…) - from rework_bpm_service_list. Block ids (from rework_bpm_service_get with includeBlocks) are strings too.job.id and job_block_id are integers - from rework_bpm_job_get (.blocks[].id = the job_block_id; status 20 = waiting on a human).A sequence is a follow-up plan for your leads: a list of steps, each on a day. Day 1 is the day a lead joins, and the waits between days are added for you. Describe the plan in plain words and your AI builds it with every step in one go.
| Step | How it runs | What your AI sets up |
|---|---|---|
| Automatic | Writes the subject and body and saves them as an email template attached to the step - or reuses a template you already have. It can reply in the thread of the previous email. | |
| Chat | Automatic | Adds the step empty, for you to write the message in the app - it depends on the chat channel you connect. |
| Call | Task for a rep | The task title, a call script, a due date and priority. |
| LinkedIn - connect, message or view profile | Task for a rep | The note or message to send. |
| SMS, personal email, direct mail | Task for a rep | The message or what to send. A personal email goes out from the rep's own mailbox. |
| To-do | Task for a rep | Any other follow-up, with a due date. |
Rep tasks go to the lead's owner unless you name someone.
Name the leads - or just their email addresses - and the sequence. Enrolling starts the sequence straight away: a day-1 email goes out within seconds, or when the sequence's sending hours next open. So your AI always shows you a preview first and enrolls only after you say yes.
A router decides what happens to a lead automatically: when it runs, then a list of steps - check a rule, give the lead an owner, wait, set an SLA deadline, or convert it to a Sales deal. Describe the routing you want; your AI checks what the funnel already has and builds it as a draft.
| Step | What it does |
|---|---|
| Gate / Branch | Only leads matching a rule go on, or matching leads take their own path while the rest continue - by source, country, tier, stage, any field. |
| Assign | To a team (round-robin, weighted, or a lead pool where the first rep to claim wins), to one person, or back to the lead's current owner. |
| SLA | A deadline (in working or calendar time). If it's missed - e.g. no call yet - remind the owner and others, reassign, or start another router. |
| Wait | Pause before the next step. |
| Convert | Create the Sales contact, and optionally a deal at a chosen stage and an account, owned by the lead's owner, a person or a team. |
A product has its own price, but quotes, orders and subscriptions sell from a price book. A product can be sold once it is listed in a book, where it gets its own price in that book.
Describe the quote in plain words. Your AI finds each product's price in your price book (volume tiers included), adds your own lines where needed, and the app works out every total.
If you sell from more than one legal entity - say three sites, three companies, three bank accounts - your AI can set each one up with its own documents. Setting up is for Commerce admins.
Discounts, taxes and fees are shared settings: every quote and order in your workspace picks from the same list. Your AI can read them, add new ones and change existing ones. Changing them is for Commerce admins.
Stock only changes through stock documents. Your AI creates the document with its lines, then posts it - the quantities change the moment it is posted.
| Document | What it does | When it is posted |
|---|---|---|
| Receipt (goods in) | Adds stock from a supplier - to an item you already hold, or as a new item in a bin | Every line is received - in full by default, at its purchase price. You can receive less, or nothing, on any line. |
| Delivery (goods out) | Takes stock out for a customer | The stock is held first; if there isn't enough available, the delivery is refused (unless the warehouse allows negative stock). |
| Transfer | Moves stock to another warehouse | Taken out at the source, then it arrives at the destination as an incoming receipt - receive it there. The goods keep their cost. |
| Stock count (adjustment) | Corrects the quantity to what you counted | Give the counted quantity; the difference is posted, with a reason such as Damaged or Periodic count. |
A form stays a private draft until you publish it. Once published, anyone with its link can fill it in - no sign-in needed.
?utm_source=facebook.Channels are where things are published - company-wide or for a team, open or invite-only. Spaces group content by kind: letters, news, foundations, events and the feed.
An automation is a trigger - a webhook, a schedule, or an event in a Rework app such as a new lead or a won deal - followed by steps that check conditions, reshape data, wait, ask for approval, notify people and create or update records, in Rework or in outside services. Each automation has a draft you edit and a live version that runs.
A service groups what can be booked - "Meeting rooms", "Company cars", "Projectors" - and sets the rules; its resources are the rooms, cars or devices themselves. A booking holds one or more resources of the same service for one time slot.
Office works in desks: the front desk (văn thư) logs what arrives or goes out, and the incoming, outgoing and internal desks handle the documents themselves. Every desk has its own stages - drafting, reviewing, approving, numbering, issuing, archiving ... - and a stage can ask people to review, approve, annotate, get a number or sign.
Sending always shows a preview first and only goes out after you confirm; drafts appear in Mail before anything is sent. Every email starts as a draft in your own mailbox.
Nothing is posted until you have seen a preview and said yes. Your AI writes as you, so every message, edit and forward - and every new room or person added - is shown to you first.
via Jolie AI (your first name), with your text below it, so the people reading it can tell it apart from messages you type in the app. It is added automatically and shown in the preview.Each team has its own goal space (a goal service in the app) - "Sales Team", "Customer Success" ... - and may group its goals on boards. A goal is an OKR or a KPI, has one owner and a period: a year, a quarter or a month.
A service is a queue of work - "IT Support", "Marketing requests" ... - and every workspace also has Direct Assignments for giving work straight to a person. Each task has one person (or team) responsible, a deadline and a priority.
Every meeting belongs to a meeting type - "Weekly team meeting", "Customer meeting" ... Internal types are for colleagues; external types can also invite people outside your workspace by email.
Workforce holds the structure the rest of Rework builds on: org units, positions (one funded seat each) and who sits in them. Approvals in other apps, payroll and who can see what follow this structure - so a change here applies there too.
HRIS is where each person's HR record lives: who they are, where and how they work, their pay and their contracts. Every employee belongs to a workspace (one per company or legal entity) and is linked to that person's Rework account. Positions and the org chart come from Workforce; HRIS links people to them.
Hiring tracks every application from the first contact to the hire. A pipeline is one kind of hiring with its own stages; an opening is a job you post in it; a candidate is one person applying to one opening.
An onboarding process is the path a new hire walks from the signed offer to day one and beyond: the steps they complete, the work the team does for them, and the emails they receive. Each new hire is then run through it in the Career app.
A schedule says who works when; a timesheet turns the days into pay figures, one period at a time. They connect through the people enrolled in both, and only published shifts count.
A policy is one kind of leave; people enrolled in it have a balance in days. A request goes through the policy's approval steps, and the balance moves only on the final approval.
An event stays a draft until you publish it. A public event is listed on your event site once published; an internal one is seen only by the people attached to it.
Every request belongs to a request type (for example Overseas Business Trip), which sets its form and who approves it. Direct Request is the free-form type where you choose the approvers yourself.
Setting up a request type (Request admins, or the type's managers): describe it and your AI creates the type, reuses a shared field where one already fits or adds new ones, builds the approval route step by step - including rules on the form's values or on who files, and approvers named by department (its head approves) or by position (whoever holds it approves), worked out each time a request is filed so a change of manager needs no change to the route - and then tries it with sample values so you can see where a request would go. Calculated fields are written as formulas - Hotel + Transport + Meals, hours between start and end minus the break, a different per-diem for overseas trips - and every formula is checked before it is saved; your AI can explain how formulas work and which fields a form offers. Types are switched off, never deleted; fields are hidden here, and removed for good in the Request app.
Analytics works inside your apps: each request names the app - Sales, Lead or Request - and uses that app's own reports, dashboards and views.
rework_bpm_*| Tool | Access | What it does |
|---|---|---|
| Discovery & identity | ||
rework_bpm_me | read | Who you are (id, name, email) - use the id to assign work to yourself |
rework_bpm_service_list | read | The services (flows) you can act on, with your rights |
rework_bpm_service_get | read | One service; includeBlocks=true also returns the full flow graph (blocks + routing) |
| Flow authoring | ||
rework_bpm_flow_edit | write | The whole flow editor in one tool - update_service · add_block · edit_block · wire (connect edges) · delete_block · validate |
| Jobs | ||
rework_bpm_job_create | write | Start a run (title; optional custom-field data, followers, tags) |
rework_bpm_job_list | read | Jobs in a service (status filter, pagination) |
rework_bpm_job_get | read | One job + live per-stage state - which block waits on a human |
rework_bpm_job_update | write | Edit a job: title, custom fields, deadline |
rework_bpm_stage_tags | write | Set the tags on a job stage (a job's tags are the roll-up of its stages') |
rework_bpm_field | write | The data fields a service collects - see what your workspace already has, who uses it, attach an existing field, add a new one, or add choices to a dropdown / multi-select field |
rework_bpm_access | read | Who can see and act on a service - its members, group access and which people own which steps, plus the rules by role. Read-only: access is changed in the app |
rework_bpm_job_advance | write | Push the waiting stage - submit a Manual form, approve / reject an Approval, or confirm / retry a paused AI step |
rework_bpm_job_cancel | write | Cancel an active job with a reason (required - it's saved on the job and posted in its discussion); its running sub jobs are cancelled too |
| Collaboration | ||
rework_bpm_discussion_create | write | Post a note on a job, or reply (threaded) - HTML content |
rework_bpm_todo | write | The checklist on a job stage - list it or add items (assignee, deadline) |
rework_pj_*| Tool | Access | What it does |
|---|---|---|
| Reads | ||
rework_pj_me | read | Who you are (id, name, email) |
rework_pj_page | read | One-call page reads - your portfolio, a project's items, milestones, phases, costs / incomes / workloads, org chart |
| Projects & boards | ||
rework_pj_project | read write | List / open projects; create, update, pin |
rework_pj_board | read write | A project's boards - add as many task boards as you need, plus issue boards |
rework_pj_group | read write | The group bands that organize a board's items |
| Work items | ||
rework_pj_item | read write | Tasks - create, assign, schedule, place on a board / stage / phase; mark done, reopen or archive; add or remove followers; open a task with its comments |
rework_pj_comment | read write | Comments - read a task's discussion with replies (newest first), post a comment or a reply; also on issues, milestones, phases, projects & backlog ideas |
rework_pj_attachment | read | Attachments - the files on a task, backlog idea, issue or document, or in its comments; Claude sees the images (screenshots, photos) and gets a link for other files |
rework_pj_issue | read write | The issue register - problems kept out of the task tree |
rework_pj_item_type | read write | The service's catalogs - work, issue, workload & income types (with rates) |
rework_pj_stage | read write | Item stages & project stages - the shared columns every project in a service moves through |
rework_pj_phase | read write | Roadmap phases - time-boxed stages with per-phase progress, workload & cost rollups |
| Plan | ||
rework_pj_milestone | read write | Milestones & outcomes |
rework_pj_backlog | read write | A ranked backlog - vote, reorder, convert ideas into tasks |
rework_pj_checkin | read write | Project status check-ins (on-track / at-risk + progress) |
| Knowledge | ||
rework_pj_doc | read write | Project documents - a tree of rich pages & folders |
| Money & reporting | ||
rework_pj_resource | read write | Bookings - workload (time), cost & income lines that drive each project's P&L |
rework_pj_output | read write | Work outputs + the done / failed reason lists |
rework_pj_report | read write | Reports, dashboards & saved board views |
| Admin | ||
rework_pj_admin | read write | Services, templates, org units & currencies |
rework_field_*| Tool | Access | What it does |
|---|---|---|
| Reads | ||
rework_field_me | read | Who you are (id, name, email) |
rework_field_page | read | One-call page reads - my day across both models, a service's overview, a plan + its visits |
rework_field_search | read | Search jobs, appointments, visits & plans |
| Setup | ||
rework_field_service | read write | The services - Visit Planning or Field Service - and the schedule board |
rework_field_account | read | Customers & contacts (live from Sales) + per-account visit history |
rework_field_template | read write | Field-service catalogs - job types, appointment types & skills |
rework_field_customfield | read write | Custom fields - add them to a visit-planning or field-service service (for that service only, or shared), then fill them on visits, jobs & appointments |
| Visit planning | ||
rework_field_plan | read write | Recurring plans - staff + accounts + recurrence, computed schedules, per-account route notes |
rework_field_visit | read write | Visits - plan ahead, check in on site, fill the visit form, check out |
| Field service | ||
rework_field_job | read write | Jobs - the customer contract; its status follows its appointments |
rework_field_appointment | read write | Appointments - create, edit, fill the work form, my queue, propose a slot |
rework_field_appointment_action | write | The crew lifecycle - dispatch, assign, check-in, check-out, no-show, reschedule, reopen + approve / decline proposals |
rework_field_dispatch | read | The dispatcher board - what needs action now, the planned week, per-staff workload |
| Operations | ||
rework_field_shift | read write | Work shifts - start / end my shift, who's on shift now, history |
rework_field_comment | read write | Comment threads on a job, appointment or visit |
rework_field_feedback | read write | Customer feedback (ratings + tags) per job or service-wide |
rework_field_report | read write | Field-service & visit-coverage reports, dashboards |
rework_prospector_*| Tool | Access | What it does |
|---|---|---|
| Inbox | ||
rework_prospector_me | read | Who you are (id, name, email) |
rework_prospector_service | read | Inbox services - the top container |
rework_prospector_channel | read | The connected provider channels (WhatsApp / Telegram / Instagram / ...) |
rework_prospector_conversation | read | Conversation threads + sidebar counts + attached files & links |
rework_prospector_message | read | Messages in a conversation, paged |
rework_prospector_profile | read | Contacts (profiles) behind conversations, with labels & fields |
| Setup | ||
rework_prospector_label | read | Labels |
rework_prospector_template · rework_prospector_canned | read | Message templates & canned responses |
rework_prospector_canned_edit | write | Create & update canned responses - for one inbox, the whole workspace or just you - with variables like the customer's name, attachments and the AI-agent switch; add many at once from a list |
rework_prospector_template_edit | write | Create & update message templates - WhatsApp, Messenger, Instagram and Zalo, with images and buttons; send WhatsApp and Zalo templates for review after you confirm a preview |
rework_prospector_agent | read write | Read and edit AI agents - persona, tone, clarification and handover instructions, which tools they use and each tool's limits (app admins; you confirm a before/after preview) |
rework_prospector_skill | read write | An AI agent's skills - list, create, edit, copy to another agent, switch on or off, reorder (app admins) |
rework_prospector_knowledge | read write | The documents AI agents answer from - add text, questions and answers or a file for chosen inboxes, update, embed again, switch on or off, and test what the AI would find (app admins) |
rework_prospector_field | read | Custom field definitions |
rework_prospector_broadcast | read | Broadcast campaigns + their recipients |
| Automation | ||
rework_prospector_flow | read write | Build & run "flows" from a plain-words request - a trigger + steps that reply, ask, branch, wait, route to a team, update fields or hand off to AI; test before you publish, then pause, run or check each run |
rework_prospector_lookup | read | The real names and ids a flow needs - inboxes, channels, stages, AI agents, people, routers, booking forms |
rework_ld_*| Tool | Access | What it does |
|---|---|---|
| Reads | ||
rework_ld_me | read | Who you are (id, name, email) |
rework_ld_service_get | read | Your lead funnels (services) and a funnel's stages, labels & blacklist |
rework_ld_lead_list | read | List & count leads in a funnel, with filters |
rework_ld_lead_get | read | One lead in full - its custom fields, activity, feed, ad attribution & associations |
rework_ld_insights | read | Cross-funnel insights - counts, trends, activity & search across services |
| Leads | ||
rework_ld_lead_edit | write | Capture & manage a lead - create, update, set a field, set owner, move stage / status, convert, blacklist, associate, bulk-edit, recalculate score |
rework_ld_lead_note | write | Write on a lead's activity stream - add a note, log a call or meeting that already happened, edit a note, pin an entry |
| Funnel setup | ||
rework_ld_leadservice_edit | write | Create & configure a lead funnel (service) |
rework_ld_field_edit | write | The custom fields a funnel collects |
rework_ld_stage_edit | write | The stages a lead moves through |
rework_ld_label_edit | write | Labels used to tag leads |
| Marketing | ||
rework_ld_campaign_get | read | Campaigns + their analytics & spend |
rework_ld_campaign_edit | write | Create & update campaigns - record spend, brief, goals, team, budget & UTM |
rework_ld_event_get | read | Gateway events + stats & routing targets |
rework_ld_event_edit | write | Route a gateway event into a lead funnel |
rework_ld_audience_create | write | Build an audience from your leads and push it to an ad provider |
| Contacts & sources | ||
rework_ld_profile_get | read | Contact profiles (people) + their timeline & activity |
rework_ld_profile_edit | write | Create & update a contact profile |
rework_ld_source_get | read | Sources & channels, the integration catalog & stats |
rework_ld_source_edit | write | Set up sources and their channels |
rework_ld_blacklist_edit | write | Blacklist rules that keep unwanted leads out |
rework_ld_salesman | read write | Salesmen - list, read, update & sync |
| Sequences | ||
rework_ld_sequence_get | read | Your sequences and what they're built from - email templates, rule sets, sender mailboxes, chat channels, and who's enrolled |
rework_ld_sequence_edit | write | Build a sequence with all its steps in one go - automatic email & chat, plus call, LinkedIn, SMS, personal-email, direct-mail & to-do tasks - then publish it |
rework_ld_sequence_template | write | Create & edit the email templates a sequence's emails use |
rework_ld_sequence_enroll | write | Put leads into a live sequence - by lead or by email address - after a preview of who goes in, which mailbox sends and when the first email leaves; pause, resume or stop one lead's run |
| Routing & SLAs | ||
rework_ld_routing_get | read | How leads are routed - routers and their steps, rules, teams (who is next, who is paused, today's caps), the lead pool, and which routers ran on a lead |
rework_ld_router_edit | write | Build a router - assign by rules to teams or people, SLA deadlines that remind or reassign, or convert qualified leads to Sales deals - as a draft, then publish it; create and edit routing rules |
rework_ld_routing_team | write | Distribution teams - round-robin, weighted or lead pool; members and their order, pause and resume people, daily / weekly caps |
rework_ld_sla_metric | write | Response-time and activity targets an SLA measures, e.g. "first reply within 15 minutes of assignment" |
rework_ld_sla_report | read | How SLAs are doing - met vs breached, compliance over time, by owner, the breaches themselves, and each router run step by step |
rework_sl_*| Tool | Access | What it does |
|---|---|---|
| Find your way around | ||
rework_sl_me | read | Who you are (id, name, email) |
rework_sl_pipeline_get | read | The CRM home (totals + your pipelines), your own work, and one pipeline as an overview or a board |
rework_sl_service_get | read | Pipelines, account & contact directories and forecast books - plus a container's stages, labels, segments, win / loss reasons and custom fields |
rework_sl_search | read | One search across deals, companies and people |
| Deals | ||
rework_sl_deal_list | read | Find deals - whole board, paged table with filters, by company or person, or just yours |
rework_sl_deal_get | read | Open one deal, with its company, primary and secondary contacts, and its stage history |
rework_sl_deal_edit | write | Create a deal, then set name / amount, owner, company, contact, labels, close date, win probability, collaborators, custom fields or files |
rework_sl_deal_lifecycle | write | Move a deal between stages or pipelines, close it won or lost with a reason, reopen it, star or follow it |
rework_sl_deal_activity | read write | What is happening on a deal beside its fields - notes on its activity (colour-coded, editable) and comments in its discussion, an action plan of tasks to assign and complete, and a history of calls, meetings and free-form entries (records only; nothing is dialled, scheduled or sent) |
rework_sl_deal_bulk | write | Apply one change to many deals at once - owner, labels, stage, custom fields, followers, mark lost or reopen |
| What is on the deal | ||
rework_sl_deal_contact | write | The extra people on a deal (the buying committee) and their role |
rework_sl_deal_product | write | Product line items - price, quantity, discount, tax |
rework_sl_deal_commerce | read | A deal's quotes and orders (read-only; build them in Commerce) |
rework_sl_product_list | read | The product catalogue, to pick a line item from |
| Companies & people | ||
rework_sl_account_list | read | Find companies - quick list, paged table, or the ones you own |
rework_sl_account_get | read | One company, its people and its deals |
rework_sl_account_edit | write | Create & update companies - fields, owner, collaborators, stage, followers, and bulk edits |
rework_sl_contact_list | read | Find people - quick list, paged table, everyone at a company, or the ones you own |
rework_sl_contact_get | read | One person and the deals they are on |
rework_sl_contact_edit | write | Create & update people - email, phone, title, their company, owner, stage, and bulk edits |
| Forecasting & analysis | ||
rework_sl_forecast | read write | Commit deals to a monthly forecast, set quotas per person, and read the quota gap |
rework_sl_report | read | Aggregate any slice of the CRM into numbers, and read your saved dashboards |
rework_sl_duplicate | read write | Find likely duplicate deals, companies or people - and merge them |
| Setting up a pipeline | ||
rework_sl_service_edit | write | Create or reconfigure a pipeline, directory or forecast book, and choose which custom fields it carries |
rework_sl_stage_edit | write | Add, rename and reorder stages - and mark which ones count as won or lost |
rework_sl_taxonomy_edit | write | Labels, segments and win / loss reasons |
rework_sl_field_edit | write | Define the custom fields your records carry - including a dropdown and its choices - then attach one to a pipeline or directory (choosing whether it shows on forms and views, and whether it is required) |
rework_sl_pipeline_admin | write | Pipeline rules (no skipping or moving backwards), currency & forecast options, required fields on close, and who can see or do what |
rework_ds_*| Tool | Access | What it does |
|---|---|---|
| Find your way around | ||
rework_ds_me | read | Who you are (id, name, email) |
rework_ds_dataset_get | read | Your tables - list them, open one, read its full set of columns and how it links to other tables, or get a one-call overview |
rework_ds_search | read | Quick search across tables, folders and rows |
| Tables & columns | ||
rework_ds_dataset_edit | write | Create a table, rename or update it, copy its structure, share it with teammates, star it |
rework_ds_schema | write | Add or remove a column, set its width, visibility, required flag and description, and reorder columns |
rework_ds_field | read write | The shared field library your columns come from - browse it; admins can add or edit fields |
| Rows | ||
rework_ds_record_get | read | Read rows - page, search, filter and sort a table, open one row in full (linked values included), or read its change history |
rework_ds_record_edit | write | Add a row and fill its cells, edit it, move it, or share it with teammates |
rework_ds_record_bulk | write | Create, update, upsert or duplicate many rows at once (up to 100) |
rework_ds_record_agg | read | Group rows and count, sum or average them without fetching every row |
| Views & folders | ||
rework_ds_view | read write | Saved views - a named filter, sort and layout - including which one is the default |
rework_ds_folder | read write | Folders that organize your tables |
rework_success_*| Tool | Access | What it does |
|---|---|---|
| Find your way around | ||
rework_success_me | read | Who you are (id, name, email) |
rework_success_service | read | Your Help Center spaces - where articles are written, and the public sites they're published to |
| Articles | ||
rework_success_hc_article | read write | List and read articles; create or edit one (title, summary, body with images, tags, category); archive it; update or publish many at once; mark one as helpful |
rework_success_asset_upload | write | Upload an image (PNG, JPG, WebP or GIF, up to 10 MB) and get the link to place in an article |
| Structure | ||
rework_success_hc_category | read write | Categories that organize your articles - they can nest |
rework_success_hc_collection | read write | Collections on your public Help Center site - where articles get published |
rework_success_hc_term | read write | Glossary terms with their definitions, alternative spellings and related terms |
| Developer docs | ||
rework_success_dev_site | read | Your developer sites; a site's table of contents with every section and page and what readers can't reach; the site as one OpenAPI document |
rework_success_dev_category | read write | Sections of the table of contents - create, rename, describe, nest, archive |
rework_success_dev_doc | read write | Guide pages - read, write (headings, code samples, tables, images), move to another section, archive |
rework_success_dev_endpoint | read write | API endpoint pages - method and path, title, description, parameters, request body, responses; mark deprecated; archive |
rework_success_dev_arrange | write | Arrange the table of contents - order and nest sections, file pages into sections - several at once, checked afterwards |
rework_success_dev_openapi_sync | read write | Bring the endpoint pages in line with an OpenAPI file: preview first, then add and update pages (drafts unless you say publish); pages missing from the file are listed, or archived if you ask |
rework_academy_*| Tool | Access | What it does |
|---|---|---|
| Find your way around | ||
rework_academy_me | read | Who you are and your workspace |
rework_academy_program | read | The training programs you can see - every course belongs to one |
| Courses | ||
rework_academy_course | read | List courses (by program, status, or the ones you teach); open one with its sections and lessons, or read one lesson in full |
rework_academy_course_edit | write | Create a course as a draft, or edit its title, description, length, learning goals, requirements, audience, cover and instructors |
rework_academy_curriculum | write | Add, rename and move sections; add, edit and move lessons - text pages, quizzes, reflection pages and video links - one change or a whole outline at once |
rework_academy_asset_upload | write | Upload an image (PNG, JPG, WebP or GIF, up to 10 MB) for a lesson or the course cover |
| Quizzes | ||
rework_academy_quiz | read | A course's quizzes; open one with its questions, the right answers and explanations |
rework_academy_quiz_edit | write | Add and edit questions, set the pass mark, retries and messages; create a final or practice exam |
rework_wf_*| Tool | Access | What it does |
|---|---|---|
| Find your way around | ||
rework_wf_me | read | Who you are (id, name, email) |
rework_wf_dashboard | read | Your dashboard - active / overdue / starred jobs and open todos, plus recent activity |
rework_wf_flowtask | read | Your task inbox - the stages waiting on you (read-only) |
| Workflows & stages | ||
rework_wf_workflow | read write | List / open workflows & the board; create or update one |
rework_wf_stage | read write | The ordered stages of a workflow - list, add, edit, reorder |
rework_wf_branch | read write | Branching rules between stages - where a job goes next depending on its fields ("if the amount is over 5,000, go to Manager approval"); read, check, set, turn on / off |
rework_wf_form | read write | The workflow's compose form - its intake & stage fields |
| Jobs | ||
rework_wf_job | read write | Jobs (work items) - list & filter, open one, create or edit it (name, content, custom fields, assignee, deadline) |
rework_wf_job_action | write | Move a job through its pipeline - advance, send back, fail, reassign, move on the board, star, archive |
rework_wf_todo | read write | A job's checklist - list yours or a job's todos, add one, tick it off |
| Set-up | ||
rework_wf_schedule | read write | Recurring schedules that spawn jobs - list, open, create / update, run now |
rework_wf_label | read write | Labels & tags for jobs on a workflow |
rework_wf_reason | read write | End-reasons shown when a job is completed or failed |
rework_mt_*| Tool | Access | What it does |
|---|---|---|
| Meetings | ||
rework_mt_me | read | Who you are (id, name, email) |
rework_mt_meeting | read | List and filter meetings, open one in full (agenda, people, answers, video link); the rooms a meeting can reserve and its room bookings |
rework_mt_meeting_edit | write | Schedule a meeting; change its time, people, agenda, location, video link or room; cancel, reopen or complete it; answer the invitation; remind an attendee |
rework_mt_service | read | Meeting types and their custom fields |
| Repeated meetings | ||
rework_mt_schedule | read | Your repeated meetings - their pattern, next date, and whether they are active, paused or archived |
rework_mt_schedule_edit | write | Set one up (daily, weekly, monthly or yearly), change it, pause, resume or archive it, or create the next meeting now |
| After the meeting | ||
rework_mt_note | read | A meeting's minutes and notes |
rework_mt_note_edit | write | Write a note into a meeting (minutes, decision, shared or private) or edit one of yours - one note per type per meeting; no deleting |
rework_mt_voting | read | A meeting's votes - options and results |
rework_mt_task | read | Action items raised in a meeting; task stats for admins |
rework_mt_recording | read | A meeting's recordings and their full transcripts |
rework_mt_file | read | Meeting files - all, yours, shared with you, annotated |
rework_mt_search | read | Search across your meetings and their notes |
rework_mt_dashboard | read | Meeting dashboards, for admins |
rework_commerce_*| Tool | Access | What it does |
|---|---|---|
rework_commerce_me | read | Who you are (id, name, email) |
| Products | ||
rework_commerce_catalog | read write | Catalogs, their category tree and labels - list, open, create, edit, retire |
rework_commerce_product_get | read | List & filter products, find one by name / code / SKU, open it with its variants, see where it is used |
rework_commerce_product_edit | write | Create & edit products (one-off or subscription price), retire them, set up options and add variants |
| Prices | ||
rework_commerce_pricebook | read write | Price books & currencies - list, open, create, edit, retire; which books apply to a customer |
rework_commerce_price_entry_get | read | Prices in a book or for a product, and the price at any quantity after rules |
rework_commerce_price_entry_edit | write | List a product in a price book, set or change its price, retire a price |
rework_commerce_price_rule | read write | Volume tiers, volume discounts & custom adjustments by quantity |
| Quotes | ||
rework_commerce_quote_get | read | List & open quotes with their lines and totals; find customers, their contacts, your selling entities, prices and available taxes, fees & discounts |
rework_commerce_quote_edit | write | Build quotes with line items, edit lines, discounts and terms, make copies, publish, get the customer link, record acceptance, cancel |
| Setup | ||
rework_commerce_entity | read write | Legal entities you sell from - list, open, create, edit (tax id, address, country, currency) |
rework_commerce_service | read write | Quote, invoice and payment services - create one, or set its default company, numbering, validity, payment terms and linked bank accounts |
| Finance | ||
rework_commerce_finance_get | read | Your discounts, taxes and fees - list, open one, and see which ones a quote can pick right now |
rework_commerce_finance_edit | write | Create and edit discounts, taxes and fees, and switch them on or off - each change is shown to you before it is saved |
rework_inventory_*| Tool | Access | What it does |
|---|---|---|
| Setup | ||
rework_inventory_me | read | Who you are (id, name, email) |
rework_inventory_warehouse | read write | Warehouses - list, open, create (Inventory admins), rename, allow negative stock, reorder defaults, document numbering, owners |
rework_inventory_location | read write | Storage locations - zones, aisles, racks, shelves & bins, many at once; the bin map of what is stored where |
rework_inventory_catalog | read | Look up products (from your Commerce catalog), suppliers and units of measure |
rework_inventory_reason | read write | Reason codes for counts, transfers and deliveries (Damaged, Expired, Customer order…) |
| Stock | ||
rework_inventory_stock_get | read | Stock levels - on hand, reserved, available, cost - and each item's movement history |
rework_inventory_stock_edit | write | Set up stock (with an opening quantity), edit its details, retire it, set its reorder point |
rework_inventory_item | read | Each item's availability across all warehouses, its recent activity and open documents |
| Stock documents | ||
rework_inventory_transaction_get | read | Receipts, deliveries, transfers and stock counts - list, search, counts by status, one document and its lines |
rework_inventory_transaction_edit | write | Create a document with its lines, then post it - receive goods, ship them, transfer between warehouses, count stock - or cancel it before it is posted |
rework_inventory_transaction_line | write | Add or change a line on a document that isn't posted yet |
| Reports & team | ||
rework_inventory_insights | read | Dashboard, low stock & what to reorder, stock value, cost of goods delivered, and the change log |
rework_inventory_comment | read write | Comments on a document or an item |
rework_form_*| Tool | Access | What it does |
|---|---|---|
| Forms | ||
rework_form_me | read | Who you are (id, name, email) |
rework_form_get | read | Find forms, open one with its questions laid out by page and section and its after-submit rules in plain words, and get its public link (pre-filled if you like) |
rework_form_edit | write | Create a form (with its questions), rename it, publish / unpublish, duplicate, pin, set its design theme, heading, submit button and spam check, save link pre-fill values, owners & followers |
rework_form_fields | write | Questions and layout - replace them all, add, change or remove one; show-if logic, link pre-fill, sections, pages and side-by-side widths |
rework_form_flow | read write | What happens after submit - rules that email, call a webhook, show a message or redirect; check them before saving |
| Responses | ||
rework_form_submission | read write | List and read responses, mark them active / spam / processed, export them, re-run the after-submit steps for one |
rework_form_insights | read | Views, responses over time and by status, and a per-question summary of the answers |
rework_form_group | read write | Folders to organise your forms - list, create, rename |
rework_townhall_*| Tool | Access | What it does |
|---|---|---|
| Read | ||
rework_townhall_me | read | Who you are, your workspace's time zone, and the Townhall spaces; optionally the people in it |
rework_townhall_feed | read | The company feed, a channel, a space or a person's posts, your saved posts, one post in full, search, posts waiting for your approval, your scheduled posts, birthdays and work anniversaries |
| Publish | ||
rework_townhall_post | write | Post or schedule an update or announcement to channels; edit, pin, follow, save; approve or reject posts in channels you manage |
rework_townhall_article | read write | Letters, news and foundation posts - list, read, draft, update, publish, unpublish or schedule |
rework_townhall_category | read write | News categories - list, create, rename, retire |
| Take part | ||
rework_townhall_comment | read write | Read and write comments and replies, edit your own, react to posts and comments |
rework_townhall_event | read write | Company events - list, read, who's coming, create, change, cancel, RSVP, invite |
rework_townhall_poll | read write | Polls - list, read, create, change, vote, add a choice, close |
rework_townhall_channel | read write | Channels - list, join, leave, favorite, invite people, create, edit, deactivate |
rework_au_*| Tool | Access | What it does |
|---|---|---|
| Read | ||
rework_au_me | read | Who you are, your workspace's time zone, and the people you can pick as approvers or recipients |
rework_au_list | read | Your automations (draft, live or paused, what starts them, last run, failures), folders, scheduled automations and when they run next, the overview, workspace variables |
rework_au_get | read | One automation - what starts it, its steps, the draft next to the live version, which steps send or change data, its versions |
rework_au_catalog | read | The steps you can use and their settings, the choices for each setting (services, pipelines, stages, fields ...), ready-made templates, your connected services (names only) |
rework_au_execution | read | Runs and their results - each step's status, output and the exact error |
| Build | ||
rework_au_build | read write | Create an automation from a description, change its draft step by step or as a whole, check it, rename or move it, copy it, start from a template |
| Test | ||
rework_au_run | write | Test the draft with sample data - the whole automation or one step - and see each step's result; steps that send or change data run only after you confirm; stop a run |
rework_booking_*| Tool | Access | What it does |
|---|---|---|
| Book | ||
rework_booking_me | read | Who you are and your workspace's time zone; optionally the people in it |
rework_booking_availability | read | What's free for a time - every room or device of a service at once, or the ones you name - and, for anything taken, why (already booked, needs a gap, too long) |
rework_booking_edit | write | Book, or change a booking's title, time, rooms, followers and form fields |
rework_booking_action | write | Cancel, check in, extend, or finish early |
rework_booking_list | read | The calendar for a day or a week, your upcoming / pending / past bookings, one room's schedule, search by title |
rework_booking_get | read | One booking in full - times, rooms, form fields, history, what you can do with it, and who still has to approve |
| Set up | ||
rework_booking_service | read write | The groups of bookable things (meeting rooms, cars ...) - their rules and booking form fields; create and edit them |
rework_booking_resource | read write | The rooms, cars and devices - create, edit, switch on / off; gap between bookings, longest booking, monthly limit, check-in, who may book |
rework_office_*| Tool | Access | What it does |
|---|---|---|
| My work | ||
rework_office_me | read | Who you are and your workspace's time zone; optionally the people in it |
rework_office_dashboard | read | What's waiting for you - reviews, approvals and annotations, tasks, number requests to decide, signatures - and what is overdue |
rework_office_flow | write | Complete your review or approval, return a document with a reason (or reject an approval), move it to another stage, and see who would take it over |
| Documents & front desk | ||
rework_office_doc | read | List documents - all, one desk, yours, archived - by stage, codes, dates or words; open one with where it stands, its history, tasks, signatures and comments |
rework_office_doc_edit | write | Create and edit documents, draft a reply, mark handled, archive, follow, link related records |
rework_office_envelope | read | What the front desk logged - list and open, with the documents it became |
rework_office_envelope_edit | write | Log, edit and register what arrived; route it to the desk that handles it (shown to you first) |
rework_office_number | read write | Registers and their numbers so far; the number a document would get; request a number or decide a request (shown to you first) |
rework_office_task | read write | Tasks from a document - your open tasks, a document's tasks; hand out, update, start, complete, cancel |
rework_office_discussion | read write | Read the comments on a document or a logged item; add a comment or a reply |
| Find & file | ||
rework_office_service | read | The desks you can see and what you may do there, their stages and form fields, and the document type / urgency / secrecy codes |
rework_office_search | read | Search documents and logged items by title, number, summary or the text of attached files |
rework_office_report | read | Statistics per desk, stage or type with a trend, the register book, and numbers issued, pending and missing |
rework_office_catalog | read write | The digital catalogs - browse and search folders; file a record into a folder or take it out |
rework_office_file | read write | File details and download links; add a file to a document; an AI summary of a file or a whole document |
rework_mail_*| Tool | Access | What it does |
|---|---|---|
| Read | ||
rework_mail_account | read | You, your connected mailboxes and your signatures |
rework_mail_inbox | read | Threads in a folder - inbox, sent, archived, trash, starred - with search |
rework_mail_thread | read | One conversation in full, with replies still waiting to go out |
rework_mail_lookup | read | Contacts you have emailed, and your email templates |
| Write & send | ||
rework_mail_template | write | Create and edit email templates, with merge fields such as the recipient's first name |
rework_mail_draft | write | Write and edit drafts - new emails or replies - with your signature if you like |
rework_mail_send | write | Send or schedule drafts, send a scheduled email now, or retry a failed one - always a preview first, sent only after you confirm |
rework_mail_outbox | read write | Scheduled and failed mail - see it, reschedule it, or cancel it back to a draft |
rework_mail_thread_action | write | Mark read or unread, star, archive, file a conversation on a Sales deal |
rework_chat_*| Tool | Access | What it does |
|---|---|---|
| Read | ||
rework_chat_me | read | Who you are and your workspace's time zone; optionally the people in it |
rework_chat_channels | read | Your channels and DMs, the rooms you used last, search rooms or people, one room with its members and sub-channels |
rework_chat_messages | read | A room's messages, the messages around one, one message, a thread's replies, search in a room, shared files - and the images attached to a message, so Claude can look at screenshots and photos |
rework_chat_inbox | read | What needs you - mentions, replies to your messages and DMs since a time |
| Write & send | ||
rework_chat_send | write | Post in a room, DM people, quote-reply, reply in a thread or under a thread reply, mention people - always a preview first, sent only after you confirm |
rework_chat_message_action | read write | Edit your message or forward one (preview first); react, pin or save; see a room's pins |
rework_chat_channel_edit | write | Create a channel or sub-channel and add people (preview first); rename a room; set how you are notified |
rework_goal_*| Tool | Access | What it does |
|---|---|---|
| Find & follow progress | ||
rework_goal_me | read | Who you are, your workspace's time zone and current quarter; optionally the people in it |
rework_goal_service | read | Your teams' goal spaces with their boards, labels, cycles and form fields, and the alignment spaces above them |
rework_goal_list | read | Find goals by team, owner, board, period, type or status - each with its progress and pace |
rework_goal_report | read | A team's, a person's or your own progress for a period: summary, per person, per board, and what needs attention |
rework_goal_get | read | One goal in full - key results with their values and progress, check-ins, reviews, followers and recent activity |
| Update | ||
rework_goal_checkin | read write | Record results - a key result's new value (one or several at once) or a KPI's score, with confidence, a note and a blocked flag; read the check-in history; fix a check-in |
rework_goal_edit | write | Set a new goal with its key results, change one, activate, complete or reopen it, follow or unfollow it |
rework_goal_key_result | write | Add a key result to a goal or change its name, target, starting value, type or weight |
| KPIs & alignment | ||
rework_goal_metric | read write | The workspace's KPI metrics, their values by period, and recording this month's or quarter's value |
rework_goal_alignment | read | Company and department targets as a tree, and one target with the team goals that contribute to it |
rework_tk_*| Tool | Access | What it does |
|---|---|---|
| Find | ||
rework_tk_me | read | Who you are and your workspace's time zone; optionally the people in it |
rework_tk_service | read | The queues tasks live in (including Direct Assignments), their form fields, end reasons, task types, duties and teams |
rework_tk_list | read | Your work (on you, handed out, followed), one queue's tasks, search by title or code, and the to-dos other apps put on you |
rework_tk_get | read | One task in full - description, status, who is responsible, deadline, checklist, sub-tasks, review and what you can do with it |
| Work | ||
rework_tk_edit | write | Hand out a task or change it - title, description, who is responsible, deadline, priority, sub-tasks, followers, checklist, form fields |
rework_tk_action | write | Start, hold, complete, cancel or reopen; ask for a review, accept it or send it back; follow or unfollow |
rework_tk_comment | read write | Read the comments on a task or a plan item, write one (@mentions notify) or reply; see the files on a task and in its comments - Claude sees the images |
| Plans | ||
rework_tk_plan | read write | Plans & OKRs - the tree with progress, check-ins with health, key-result values, link or unlink tasks |
rework_workforce_*| Tool | Access | What it does |
|---|---|---|
| Organisation | ||
rework_workforce_me | read | Who you are and your workspace's time zone |
rework_workforce_org | read write | The org chart as a tree, or one unit in full; add, rename, move or reorder units and set their head and members - one or many at once |
rework_workforce_people | read write | Find people by name, email or team; one person's positions, teams and office; set offices, one or many at once |
rework_workforce_relations | read write | A person's managers and peers, who reports to someone; set them for one person or hundreds at once |
rework_workforce_catalog | read write | Job profiles, job families, grades, locations, cost centers and operation roles; add, edit or retire them, one or many at once |
| Positions | ||
rework_workforce_position | read write | Find and open positions with who holds them; create or edit one, mark an empty one as eliminated, or create and update hundreds at once |
rework_workforce_assignment | read write | Assign someone to a position, hand it to someone else or end it - one or many at once; the history of a position or a person |
| Planning | ||
rework_workforce_plan | read write | Headcount plans, their items and scenarios; add, edit, approve, turn into a position or cancel an item |
rework_workforce_budget | read write | Headcount and cost caps per team or cost center |
| Results | ||
rework_workforce_output | read write | Outputs and hours - where to log them, read them by period, team or person, log or edit yours |
rework_workforce_monitor | read write | KPI monitors and their check-ins; check in a value for a month, a quarter or a year |
rework_hris_*| Tool | Access | What it does |
|---|---|---|
| Set-up | ||
rework_hris_me | read | Who you are, the company record and the workspaces you can see - the place to start |
rework_hris_setup | read write | Workspaces, offices, employee types, pay policies (tax, insurance, benefits), salary components and reasons for leaving - list, create, edit, retire |
rework_hris_service | read write | HR types: contract types (with automatic numbering and probation rules), termination, leave, document and change-request types |
| People | ||
rework_hris_employee | read write | Find employees, open a full profile, add a new hire, update work / personal / legal details, set pay and bank account, move many people at once |
rework_hris_import | read write | Bulk import from rows - employees and their details, contracts, job profiles, policies, leaves, terminations, change and document requests, assets - checked before anything is saved |
rework_hris_contract | read write | Contracts - list, open, create, edit, mark signed, make current, send for e-signature or by email (after a preview) |
rework_hiring_*| Tool | Access | What it does |
|---|---|---|
rework_hiring_me | read | Who you are, the pipelines you can see with their stages, and the candidate sources |
rework_hiring_pipeline | read write | Pipelines and their stages - list, open, create with stages, rename, add / edit / reorder stages |
rework_hiring_catalog | read write | Labels and reject reasons per pipeline, candidate sources for the company |
rework_hiring_opening | read write | Job openings - list, open, write as a draft, edit, publish or reopen (after a preview), close |
rework_hiring_candidate | read write | Candidates - list, open with evaluations and notes, add, edit, move to a stage, reject with a reason, add a note |
rework_hiring_report | read | Hiring funnel, sources, time to hire and recruiter activity |
rework_career_*| Tool | Access | What it does |
|---|---|---|
rework_career_me | read | Who you are and the Career processes you can see, by kind |
rework_career_onboarding | read write | Onboarding processes - list, open with steps and hires per stage, create, add / edit / switch off / reorder steps, apply templates, set the emails and options |
rework_timesheet_*| Tool | Access | What it does |
|---|---|---|
| Set-up | ||
rework_timesheet_me | read | Who you are, the services and check-in channels you can see, and the order to set things up in |
rework_timesheet_service | read write | Schedule and timesheet services - list, open, create, edit, restore |
rework_timesheet_catalog | read write | Shift types, shift blocks, working areas, symbols and holidays |
rework_timesheet_channel | read write | Check-in channels and personal check-in codes |
rework_timesheet_pattern | read write | A schedule's working pattern, pattern templates, and what still blocks generating shifts |
rework_timesheet_enrollment | read write | Who is on which schedule, timesheet or overtime policy - enrol one or many |
rework_timesheet_pay_rule | read write | Pay rule sets, a timesheet's rules and their history, copy and apply, pay settings |
rework_timesheet_overtime_setup | read write | Overtime policies, purposes and request templates |
| Running it | ||
rework_timesheet_shift | read write | Shifts - list, create, edit, assign, apply in bulk, copy, offer open shifts |
rework_timesheet_schedule | read write | Generate a month of shifts, publish them, coverage, best-fit people, auto-fill (after a preview) |
rework_timesheet_attendance | read write | Attendance logs and daily summaries; add, edit or void a punch with a reason |
rework_timesheet_submission | read write | Check-in requests - file, approve, reject, cancel |
rework_timesheet_overtime | read write | Overtime requests - file, approve, reject, confirm, in batches; hours against limits |
rework_timesheet_exchange | read write | Shift swaps and hand-overs - find candidates, file, decide |
| Periods | ||
rework_timesheet_cycle | read write | Timesheet periods - open, checks, move to Review, correct day values, waive a check, reopen; the final lock points you to the app |
rework_timesheet_delivery | read write | Email people their timesheets (after a preview), export to Excel, PDF or Word |
rework_timeoff_*| Tool | Access | What it does |
|---|---|---|
rework_timeoff_me | read | Your leave types and balances, your requests, your shifts |
rework_timeoff_request | read write | File a leave request - check it first, submit after you agree, cancel while it waits |
rework_timeoff_approval | read write | What is waiting on you, request details, approve or reject (also in bulk), comments |
rework_timeoff_policy | read write | Leave policies and templates - list, open with approval steps, read a draft's rules in plain words without saving, create (a policy that would earn nothing is refused), edit |
rework_timeoff_enrollment | read write | Who is on which policy, enrol one or many, balance history, add or adjust days, import opening balances |
rework_timeoff_report | read | Leave taken, accrued liability, expiring balances, cash-outs, holidays |
rework_rq_*| Tool | Access | What it does |
|---|---|---|
| Find | ||
rework_rq_me | read | Who you are (id, name, email) and your workspace's timezone |
rework_rq_service | read | The request types you can use, and one type's form (fields, required ones, choices) and approval steps |
rework_rq_request_list | read | Your requests by inbox - waiting on you, sent, to approve, following, bookmarked - with filters, paging and totals |
rework_rq_search | read | Find requests and request types by words or request number |
rework_rq_request_get | read | One request in full: form, attachments, every approval step and note, activity, and what you can do now |
| File | ||
rework_rq_request_form | read | Prepare a request: the request type's own form, instructions and approval route (incl. its rules), what is still missing, and where the request would go - nothing is filed |
rework_rq_request_create | write | File the prepared request - checked again first, its files attached; if anything is missing or the app refuses, nothing is filed and you are told why. Or save it as a draft |
rework_rq_draft | read write | Your drafts - list, open, change only what you mention, and file one |
rework_rq_schedule | read write | Requests that file themselves daily, weekly or monthly - preview the next dates, create, change, pause or resume |
| Act | ||
rework_rq_decide | write | Approve, reject, forward or send back a request waiting on you, with a note and any fields approvers fill |
rework_rq_request_edit | write | Edit your request, restart its approval, resend it after it was sent back, duplicate it, follow it, add followers, bookmark it, or void it (admins) |
rework_rq_discussion | read write | Read and write comments and posts on a request, and reply to a comment |
rework_rq_report | read | Request statistics - overall, per request type, and per type totals (Request admins) |
| Set up (admins) | ||
rework_rq_setup_service | write | Create and change request types - name, description, group, managers, default followers, who can see and file them (people, departments, positions or privilege groups), numbering, SLA - switch them on or off, and manage the groups |
rework_rq_setup_form | read write | A request type's form - list its fields, reuse a shared field, add new ones (text, numbers, dates, choices, people, files, tables, formulas and conditional formulas ...), rename, change choices, formulas or table columns, make required or hide - plus a guide to writing formulas |
rework_rq_setup_approval | read write | A request type's approval route - set it in one go or step by step: fixed approvers, steps where the filer tags someone, direct managers, rule-based steps, AI workers - approvers can be people, a department's head or a position's holder; plus notes required, supreme approvers and followers added by rules, and the list of departments and positions to choose from |
rework_event_*| Tool | Access | What it does |
|---|---|---|
| Events | ||
rework_event_me | read | Who you are (id, name, email) and your workspace's timezone |
rework_event_setup | read | Programmes, organizers (with their subscriber count), event presets and currencies |
rework_event_list | read | Find events by status, format, type, programme, organizer, name or date range |
rework_event_get | read | Open an event in full, its live numbers, its setup checklist, its team, and the other dates of a recurring event |
rework_event_edit | write | Create an event, change only what you mention, duplicate it to a new date, set its team, add or remove an online meeting link, turn features on or off |
rework_event_status | write | Publish, unpublish, close, reopen, take offline or bring back - asks first when publishing would email subscribers |
| Tickets, agenda & speakers | ||
rework_event_ticket | read write | Free, paid or donation tickets - create, change, show / hide, reorder |
rework_event_agenda | read write | Agenda sessions with times, tracks, rooms and speakers; who signed up for a session |
rework_event_speaker | read write | Your speaker and sponsor library, and who is linked to an event |
| Guests | ||
rework_event_guest | read | The guest list, exact filters, one guest's full profile, quick search, headline numbers, check-ins, orders and the waitlist |
rework_event_guest_edit | write | Add a guest, load a list of guests, edit a guest, check someone in or undo it |
rework_insight_*| Tool | Access | What it does |
|---|---|---|
| Find & ask | ||
rework_insight_catalog | read | Which apps you can report on, their data sources and who may create dashboards there - plus the people you can share with |
rework_insight_schema | read | What a data source can count, sum or average, group by (custom fields included), break down by date, and filter on |
rework_insight_compute | read | The numbers for a question - measures, grouping, a date breakdown and filters - without saving anything |
| Dashboards | ||
rework_insight_dashboard_get | read | Your dashboards, or one dashboard with its charts, their layout and who it is shared with |
rework_insight_dashboard_edit | write | Create, rename, arrange or copy a dashboard |
rework_insight_widget_edit | write | Add a chart, change it or copy it - the question you asked, saved with its chart type and its own filters |
rework_insight_dashboard_share | write | Add or remove the people who may view or co-edit a dashboard |
| Views & layouts | ||
rework_insight_view_get | read | The saved views on a pipeline, directory or lead service, and the sort options a view keeps |
rework_insight_view_edit | write | Create and change a saved view - filters, sort, columns - star it, share it with the team, make it the default, switch it off or on, reorder |
rework_insight_layout | read write | How a deal or lead page is laid out - templates, sections and blocks; save one or make it live (managers) |