Worker records
Name, job title, department and start date from the Rippling worker read, used when a question needs the current worker.
Connect Rippling so PaperThread can answer worker questions and surface leave signals from the worker record.
Name, job title, department and start date from the Rippling worker read, used when a question needs the current worker.
Leave requests from Rippling show time away that a case needs to see.
First name, last name, work email, job title, department and start date can be updated only where the Rippling connection permits it.
Rippling worker reads do not include bank details, so PaperThread does not flag bank gaps from this connection.
Answer worker questions from the Rippling worker record.
Prepare a follow-up from a leave signal.
Send the next step to the person who owns it.
Update first name, last name, work email, job title, department or start date only where permitted. Bank details are not part of this connection.
Assign a person when Rippling cannot finish the action.
Answers for this connection, including what PaperThread can read and what still needs a person.
Another HRIS people record when the worker is not held in Rippling.
The private DM where a Rippling question, nudge or approval can be sent.
Approved policy files that sit alongside Rippling worker context.
Hiring status that can start onboarding follow-up against the Rippling worker record.
Answer from the Rippling record and surface leave, and keep anything the connection cannot finish with a person.