Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

SignNow

eSignature platform for sending, signing, and managing documents.

CategoryProductivity
AuthenticationOAuth 2.0, custom
Version0.0.6
Published scopes1 published scope
Last updatedSeptember 30, 2026

Overview

Connect SignNow with Flows360

eSignature platform for sending, signing, and managing documents.

Use the SignNow connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 5 triggers.

Available actions

  • Cancel Invite to Sign
  • Upload Document
  • Upload Document & Extract Fields
  • Invite to Sign
  • Create Document From Template & Send Free Form Invite
  • Create Document From Template & Send Role-Based Invite
  • Create Document Group From Template Group & Send Invite
  • Custom API Call

Available triggers

  • New Document
  • Document Updated
  • Document Completed
  • Document Deleted
  • Document Group Completed

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: SignNow
  • Package: @activepieces/piece-sign-now@0.0.6
  • Exact artifact digest: sha256:3f1cc0879c5071e11b99af77da9fc218c92228b09cc157b0cb94a82c49605315
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2, CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Cancel Invite to Sign (cancel_invite), Cancels an invite to sign a document. Classification: read.
  • Upload Document (upload_document), Uploads a document to your SignNow account. Supports PDF, Word, PowerPoint, Excel, images, and more. Classification: read.
  • Upload Document & Extract Fields (upload_document_and_extract_fields), Uploads a document and automatically converts text tags into SignNow fillable fields. Classification: read.
  • Invite to Sign (send_invite), Sends an invite to sign an existing document. Classification: read.
  • Create Document From Template & Send Free Form Invite (create_document_from_template_and_send_invite), Creates a new document from a template and sends a free form invite to a signer. Classification: read.
  • Create Document From Template & Send Role-Based Invite (create_document_from_template_and_send_role_based_invite), Creates a new document from a template with fillable fields and sends an invite to one or more signers by role. Classification: read.
  • Create Document Group From Template Group & Send Invite (create_document_group_from_template_and_send_invite), Creates a new document group from a template group and sends an invite to one or more signers. Classification: read.
  • Custom API Call (custom_api_call), Make a custom authenticated request to any SignNow API endpoint. Classification: read.

Trigger contracts

  • New Document, webhook.
  • Document Updated, webhook.
  • Document Completed, webhook.
  • Document Deleted, webhook.
  • Document Group Completed, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationOAuth 2.0, custom
Supported objects13
Supported actionsNot published
Triggers5

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

*

Authentication profiles

connection · oauth2

OAuth scopes: *

connection_2 · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Cancel Invite to Sign Yes No Cancels an invite to sign a document.
Upload Document Yes No Uploads a document to your SignNow account. Supports PDF, Word, PowerPoint, Excel, images, and more.
Upload Document & Extract Fields Yes No Uploads a document and automatically converts text tags into SignNow fillable fields.
Invite to Sign Yes No Sends an invite to sign an existing document.
Create Document From Template & Send Free Form Invite Yes No Creates a new document from a template and sends a free form invite to a signer.
Create Document From Template & Send Role-Based Invite Yes No Creates a new document from a template with fillable fields and sends an invite to one or more signers by role.
Create Document Group From Template Group & Send Invite Yes No Creates a new document group from a template group and sends an invite to one or more signers.
Custom API Call Yes No Make a custom authenticated request to any SignNow API endpoint.
New Document Yes No webhook trigger declared by the pinned package.
Document Updated Yes No webhook trigger declared by the pinned package.
Document Completed Yes No webhook trigger declared by the pinned package.
Document Deleted Yes No webhook trigger declared by the pinned package.
Document Group Completed Yes No webhook trigger declared by the pinned package.

Triggers

New Document · Webhook

Triggers when a document has been uploaded to SignNow.

Document Updated · Webhook

Triggers when a document has been updated.

Document Completed · Webhook

Triggers when all signers have filled in and signed the document.

Document Deleted · Webhook

Triggers when a document has been deleted.

Document Group Completed · Webhook

Triggers when all signers have filled in and signed the document group.

Setup

Setup

  1. Add the SignNow connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API Key (apiKey), required; stored as a sensitive connection value.

OAuth scopes

  • *
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-sign-now@0.0.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required SignNow connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-sign-now@0.0.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com