This Flowbot example demonstrates how to send CloudSign reminders, update information, and notify the internal team when specific conditions and dates are met.

✔️ Yoom Database - Stores contract records and related data.

✔️ Schedule trigger - Initiate the Flowbot at a set time.

✔️ Data Manipulation/Transformation - Adjusts dates for comparisons.

✔️ Database Operation - Retrieves and updates records in YoomDB.

✔️ Repeat Command - Process multiple records individually.

✔️ CloudSign App - Sends reminders for unsigned contracts.

✔️ ChatWork App - Notifies the internal team when a reminder is sent.

This process applies to scenarios where documents have already been sent via CloudSign. The system searches YoomDB for contracts that remain unsigned after a week and then sends a reminder.

1️⃣ Trigger Flowbot

A schedule trigger is set to run the Flowbot at 10:00 AM on business days.

2️⃣ Identifying Unsigned Documents

The data manipulation operation generates a date one week prior to today, helping to identify contracts that have remained unsigned for over a week.

3️⃣ Retrieving Targets from YoomDB

The database operation fetches all records where the contract is still unsigned after a week.

4️⃣ Handling Cases with No Unsigned Contracts

A branch command determines whether any targets exist:

5️⃣ Processing each Record Individually

The repeat command processes each retrieved record one by one.

6️⃣ Sending Reminders via CloudSign

The CloudSign app sends a reminder email to each company with an unsigned contract.

7️⃣ Logging the Reminder Date in YoomDB

The database operation updates the reminder log to track when a reminder was sent.

8️⃣ Notifying the Internal Team

A Chatwork notification informs the team that reminders were sent.