- How to add a new row on Retable for a newly signed envelope in Signeasy
- 1. Create your playbook and set the Signeasy trigger as "Envelope signed"
- 2. Add the "Add row to table" in Retable automation
- 3. Activate your Relay.app playbook
- Learn more about integrating with Retable and Signeasy
- Related blog posts
- More how-to guides featuring Retable and Signeasy
How to add a new row on Retable for a newly signed envelope in Signeasy
Create your playbook and set the Signeasy trigger as "Envelope signed"
After creating your playbook, you can proceed to add your trigger. The trigger detects changes in your connected apps and responds to your playbook.
To set up this playbook, click "Add trigger" and then select "Envelope signed" under Signeasy. Then, select details like name. This will allow your playbook to automatically detect the newly signed envelope in Signeasy and initiate necessary actions.
If this is your first time using a Signeasy integration in Relay.app, a prompt will guide you through the connection process.
Add the "Add row to table" in Retable automation
Integrate the Retable automation into your playbook to ensure the prompt addition of a new row in Retable when a new envelope has been signed in Signeasy.
Click the "Add step" button, then locate the "Add row to table" automation for Retable and input the mandatory and relevant details.
If your Retable account isn't already connected to Relay.app, you will be prompted to complete that connection. Make sure to allow the necessary permissions for Relay.app to sync with your Retable account.
Activate your Relay.app playbook
Activating your playbook is the final step to automate the addition of a new row in Retable. Once turned on, it will respond to each newly signed envelope in Signeasy by adding a new row in Retable without manual intervention.
To enable your playbook, click the toggle button located in the header. It is advisable to perform a test run of your playbook beforehand to ensure all steps work seamlessly together and reminders are being sent correctly.