Trigger
Schedule — a CRON expression runs the workflow weekly (e.g.0 8 * * 1 for every Monday at 8 AM).
Workflow
Fetch recently signed agreements
An API Request step calls the e-signature platform’s API to list agreements completed in the past 7 days. Most platforms support filtering by status (
completed / signed) and date range.Filter already-ingested agreements
A Database step reads the
ingested_agreements table in an automation database to get previously processed envelope or agreement IDs. A Code step filters the list, removing any that have already been uploaded.Loop over new agreements
A Loop step iterates over the remaining agreements. Inside each iteration:
- Download the signed PDF — an API Request step fetches the completed document from the e-signature platform’s download endpoint.
- Upload to Royaltyport — an API Request step with the Royaltyport API preset uploads the file to the target project. Royaltyport’s extraction pipeline processes the contract automatically.
Mark as ingested
A Database step inserts the agreement ID, signing date, and Royaltyport contract ID into the
ingested_agreements table so it is skipped on future runs.Key Features Used
- Schedule trigger for weekly polling
- Automation database for deduplication tracking
- Code step for filtering already-ingested agreements
- Royaltyport API for automated contract upload
- Loop to process multiple agreements in a single run
Related Documentation
API Request
Configure API calls to e-signature platforms and Royaltyport.
Databases
Track ingested agreements to prevent duplicates.
Contract Upload API
Upload contracts programmatically via the REST API.
More Examples
Browse all example workflows.