Employee roster
Employees from Staffology, used when a payroll question needs the current person.
Staffology + PaperThread
Connect Staffology so PaperThread can answer payroll questions and flag an upcoming pay cutoff when Staffology returns a cutoff date.
How it integrates with Staffology.
Pay cutoffs
PaperThread uses a cutoff date on the pay run when Staffology returns one. It does not invent a cutoff when that date is missing.
Read only
PaperThread reads Staffology employees and pay runs. It does not write employee or pay fields back.
No bank read
Staffology employee reads do not include bank details, so PaperThread does not flag bank gaps from this connection.
How PaperThread puts that
context to work.
Read context
Answer payroll questions from Staffology employees and pay runs.
Prepare actions
Prepare a follow-up when a confirmed cutoff date is approaching.
Route work
Send the next step to the person who owns it.
Update supported items
PaperThread does not write employee or pay fields back to Staffology. Bank details are not written.
Hand off to a person
Assign a person when Staffology 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 payroll questions from Staffology and flags an upcoming cutoff when Staffology returns a cutoff date. PaperThread does not invent a cutoff date.
Employees and pay runs. A cutoff is flagged only when a cutoff date is present. Bank details are not part of this connection.
No. PaperThread does not write employee fields or pay fields back to Staffology. A change that Staffology must store stays with a person.
No. Staffology stays the payroll system. PaperThread uses that record to answer payroll questions, flag a confirmed cutoff, and keep the case with a person when needed.
PaperThread keeps the case open, assigns a human step, and records what still needs to happen. An unsupported Staffology action is not marked done.
A workspace admin enters a Staffology API key and employer ID. The key is stored in the credential vault. This connection uses basic authentication, not OAuth.
Related integrations
Browse all integrations →
HiBob
HRIS people context when a Staffology question needs the employee record.
Slack
The private DM where a Staffology cutoff 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 Staffology payroll context.
Sage Payroll
Another payroll source when the pay run is not held in Staffology.
Connect Staffology to PaperThread.
Answer payroll questions from Staffology, flag a confirmed cutoff date, and keep anything the connection cannot finish with a person.