Getting Started with the OP.Sign for app integration

Setting up OP.Sign within is easy

  1. Select the OP.Sign integration

  2. Select your formula

  3. Connect your OP.Sign account

  4. Configure your formula
  5. Start working

Let's begin!

Copy of app store icon 200px.png


1. Select the OP.Sign integration

Within your board, click on the Integration icon (the electric plug icon at the top right of the screen), The Integration Center opens. 
In the search box type OP.Sign and click on the only result:  Send to Sign 

2. Select your formula

There are four available formulas

Two are based on Status change triggers and two on Periodical triggers.

Status changes triggers are for sending out documents for signature when the status is right.

For example, a contract is automatically sent to sign when the responsible person in your organisation changes the contract status field to Ready to Send 

Periodical triggers are for sending out documents for signature when the time is right.

For example, a purchase requisition could be sent to the financial director every Thursday at 9am.

Once you determined which of the two is more suitable for you, it's time to make another selection: there is one formula for linked source documents and one formula for attached documents.

How to choose your formula

  1. Will you be working on status changes triggers or periodical triggers?

  2. Do you wish your documents to be attached to the board or to include a link to the document (which resides in a cloud drive of an https url)

3. Connect your OP.Sign account

Once you select your formula, you'll be redirected to the OP.Sign login page.

You'll be asked to login with the account you wish to be used for OP.Sign in the context. 

If you do not have an OP.Sign account, don't worry. Sign Up is just one click and 4 form fields away. 

4. Configure your formula

Once you selected the formula and linked to the OP.Sign account, you need to configure your formula to match the specifics of your board.

Let's take one formula and analyse it:


When the Status changes to Value send the Link to the recipient's Email for signature.

When the doc is signed, add the signed doc into Signed Doc and change the Status to Success or Failure.

Before going field by field, let's see what the recipe does. For this example, we'll use an HR board containing info on candidates for a specific role:

The board includes the name field, the role field and some other fields, including the Link field that contains the candidate's employment contract and the email field containing the candidate's email address.
So, when a candidate has passed the appropriate steps in the hiring process and the company informed her a contract is on the way, the HR person goes to the candidate's row in the the board and changes the status to "Ready to Send".
Then, the OP.Sign app kicks in, sending the contract to the candidate to sign.
The signautre process takes place in the OP.Sign mobile app or Web interface.
After the candidate signs, the OP.Sign app updates the board's status field accordingly and adds a link to the signed contract to the Signed Doc filed.


Field by field analysis:

Status - this is the field of type status.
We see it twice in the formula,

  • First when we set the trigger for automation - "When the Status changes to Value..."​​ the value can be "Ready to Sign", Send for Signature", "Pending Approval" or anything else that makes sense to you.

  • Then when the signing activity in OP.Sign is done and the board is updated accordingly "...change the Status to Success or Failure"
    as the recipient can Sign the document or ask for it to be revised before signing, OP.Sign captures both types of events and updated the board accordingly


  • Please note: allows you to add more than one status field per board - make sure you are using only one status field (the same one) for both initiating OP.Sign and for receiving the OP.Sign update at the end of the process

Link and Signed Doc - both fields are the field of type Link, meaning the document resides in another location and the content of the link field contains that location.

For the Link column, the link can be to DropBox, G Drive or OneDrive, you can choose the service that suitable for you (probably the one that you're already using)
When doing so, make sure the document have appropriate permissions, for everyone with the link or specifically for the email you used to sign into OP.Sign, to view the document.
Otherwise, OP.Sign won't be able to access the document and this will result in an error.
You can also us an https link to a cloud storage drive (e.g.: AWS S3), in this case make sure you are using a direct link to the document and not an html wrapper of some sort.

For the Signed Doc column, the content of the link is the Signed document - the document that was previously sent for signature, after the signers applied their signature on it.

Email - this is the field of type email. 

5. Start working

Now you can integrate OP.Sign in your boards.
good luck and happy signing!

For any issues or questions, please send us a note to with the words "Using OP.Sign with" in the title and describe the issue you encountered.

We're here to help!