PaperThread

Rippling + PaperThread

Connect Rippling so PaperThread can answer worker questions and surface leave signals from the worker record.

Rippling logo
PaperThread

How it integrates with Rippling.

Worker records

Name, job title, department and start date from the Rippling worker read, used when a question needs the current worker.

Leave signals

Leave requests from Rippling show time away that a case needs to see.

Allowed updates

First name, last name, work email, job title, department and start date can be updated only where the Rippling connection permits it.

No bank read

Rippling worker 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 worker questions from the Rippling worker record.

Prepare actions

Prepare a follow-up from 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, job title, department or start date only where permitted. Bank details are not part of this connection.

Hand off to a person

Assign a person when Rippling 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 worker questions from the Rippling record and surfaces leave signals, so the next step uses the current worker rather than a pasted export.

Connect Rippling to PaperThread.

Answer from the Rippling record and surface leave, and keep anything the connection cannot finish with a person.