People records
Name and work email from the Factorial employee read, used when a question needs the current employee.
Factorial + PaperThread
Connect Factorial so PaperThread can answer people questions, flag bank gaps, and surface leave signals from the employee record.
How it integrates with Factorial.
Bank gaps
The employee bank number is read, including an IBAN when that is the format, so gaps can be flagged. PaperThread does not write bank details back.
Leave signals
Time-off changes from Factorial show leave that a case needs to see.
Allowed updates
First name, last name, work email and location can be updated only where permitted. Job title and department are not written on the employee record.
How PaperThread puts that
context to work.
Read context
Answer people questions from the Factorial employee record.
Prepare actions
Prepare a follow-up from a bank gap or a leave signal.
Route work
Send the next step to the person who owns it.
Update supported items
Update first name, last name, work email or location only where permitted. Job title, department and bank details are not written.
Hand off to a person
Assign a person when Factorial cannot finish the action.
Common questions, clear answers.
Answers for this connection, including what PaperThread can read and what still needs a person.
It answers people questions from the Factorial record, flags bank gaps, and surfaces leave signals, so the next step uses the current employee rather than a pasted export.
People fields, the employee bank number, and time-off. An IBAN clears the bank check when that is the stored format. Bank details are read so gaps can be flagged.
Only where permitted, and only for first name, last name, work email or location. PaperThread does not write job title, department, bank number or national identifier back to Factorial.
No. Factorial stays the system of record for employee data. PaperThread uses that record to answer, flag bank gaps, surface leave, and record the PeopleOps work around it.
PaperThread keeps the case open, assigns a human step, and records what still needs to happen. An unsupported Factorial action is not marked done.
A workspace admin enters an admin-scoped Factorial API key. The key is stored in the credential vault. This connection does not use Factorial OAuth.
Related integrations
Browse all integrations →
Plumm
Another HRIS people record when the employee is not held in Factorial.
Slack
The private DM where a Factorial question, nudge or approval can be sent.
'%3e%3cpath%20d='M21.1684%20214.263L33.5166%20235.577C36.0825%20240.064%2039.7709%20243.59%2044.1008%20246.154L88.2016%20169.872H0C0%20174.84%201.28293%20179.808%203.8488%20184.295L21.1684%20214.263Z'%20fill='%230066DA'/%3e%3cpath%20d='M140%2080.1282L95.8992%203.84616C91.5693%206.41026%2087.8809%209.9359%2085.315%2014.4231L3.8488%20155.449C1.33012%20159.839%200.00335347%20164.811%200%20169.872H88.2016L140%2080.1282Z'%20fill='%2300AC47'/%3e%3cpath%20d='M235.9%20246.154C240.23%20243.59%20243.919%20240.064%20246.484%20235.577L251.616%20226.763L276.152%20184.295C278.718%20179.808%20280.001%20174.84%20280.001%20169.872H191.793L210.562%20206.731L235.9%20246.154Z'%20fill='%23EA4335'/%3e%3cpath%20d='M139.999%2080.1282L184.1%203.84615C179.77%201.28205%20174.799%200%20169.667%200H110.331C105.2%200%20100.228%201.44231%2095.8984%203.84615L139.999%2080.1282Z'%20fill='%2300832D'/%3e%3cpath%20d='M191.799%20169.872H88.2024L44.1016%20246.154C48.4315%20248.718%2053.4028%20250%2058.5346%20250H221.467C226.599%20250%20231.57%20248.558%20235.9%20246.154L191.799%20169.872Z'%20fill='%232684FC'/%3e%3cpath%20d='M235.418%2084.9359L194.685%2014.4231C192.119%209.9359%20188.431%206.41026%20184.101%203.84616L140%2080.1282L191.798%20169.872H279.84C279.84%20164.904%20278.557%20159.936%20275.991%20155.449L235.418%2084.9359Z'%20fill='%23FFBA00'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_9984_29122'%3e%3crect%20width='280'%20height='250'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e){kind=small}
Google Drive
Approved policy files that sit alongside Factorial employee context.
Gusto
Payroll context for pay questions that start from a Factorial employee record.
Connect Factorial to PaperThread.
Answer from the Factorial record, flag bank gaps, and surface leave, and keep anything the connection cannot finish with a person.