Skip to main content

Make Waves ’26. Find out everything we’ve announced to build a more transparent future for AI agents in business

Read now (opens in a new tab)
Sign
Apify

Connect Sign and Apify integrations

Explore ready-made Sign and Apify templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Sign with Apify and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Sign
Trigger: Watch Processes
Apify
Action: Select an action
1. Select a trigger

  • Triggers everytime time one of these actions is performed on a document: signed by a signer | rejected by a signer | process cancelled | process finished. The updates are always sent back.

2. Select an action

  • Performs an arbitrary authorized API call.

  • Runs a selected Actor task.

  • Run a selected Actor.

  • Run a selected Actor.

  • Deprecated, please use Web Fetch instead, which fetches a page in a single request without running a scraper. Runs a scraper for the website and returns its content as text, markdown and HTML.

  • Fetches the content of a web page, PDF or file and returns it as markdown, plain text, HTML, links or raw content. It gets past bot protection in a single request, which makes it a good fit for large language model (LLM) flows.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Sign and Apify.

Cancel a Signing Process
Cancel an existing sign process. Cancellation is only possible if there exists at least one participant that did not yet sign or reject his/her signature.
Action
Cancels a Process (UI Based)
Cancels and deletes a draft document created through the UI Wizard
Action
Encode a Document to Base64
Encodes any document with text in Base64.
Action
Find a Process By Original Document
Checks if the provided document was used in a signing process.
Action
Get Dataset Items
Fetches items from a dataset.
Search
Get Finished Document by ID
Delivers the finished document for a given ID, with certificate header and all performed signatures.
Action
Get Process Information
Gets the meta data and process information for a given document ID.
Action
Get the Current User
Retrieves information about the current user
Action
Initiate a Draft Process (UI Based)
Creates a draft signing process to be completed within the UI-Wizard.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.