Active with remarks |
---|
This application needs additional settings. Please follow the documentation below to create your own connectionUnique, active service acces point to a network. There are different types of connections (API key, Oauth…). More. |
From creating contracts to keeping track of the signed ones, the eSignatures.io modulesThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More enable you to easily automate your contract sending process from start to finish.
Prerequisites
-
An eSignatures.io account
In order to use eSignatures.io with Boost.spaceCentralization and synchronization platform, where you can organize and manage your data. More IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. More, it is necessary to have an eSignatures.io account. If you do not have one, you can create an eSignatures.io account at esignatures.io.
Note | |
---|---|
The moduleThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More dialog fields that are displayed in bold (in the Boost.space Integrator scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. More, not in this documentation article) are mandatory! |
To connect your eSignatures.io account to Boost.space Integrator you need to obtain the Secret TokenThe API token is a multi-digit code that allows a user to authenticate with cloud applications. More from your eSignatures.io account and insert it in the Create a connection dialog in the Boost.space Integrator module.
1. Log in to your eSignatures.io account.
2. Go to API settings in the top-right corner.
3. Copy the Secret Token to your clipboard.
4. Go to Boost.space Integrator and open the eSignatures.io module’sCreate a connection dialog.
5. In the Connection name field, enter a name for the connection.
6. In theSecret Token field, enter the token details copied in step 3, and click Continue.
The connection has been established.
All triggersEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... need a webhookA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. in order for them to functionFunctions you can use in Boost.space Integrator - create, update, delete, get, search.. In your eSignatures.io module, choose any of the triggers then generate a webhook. This will automatically connect the webhook from Boost.space Integrator to your eSignatures.io account.
TriggerEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... Options |
Description |
Watch Contract Sent To Signer |
Triggered when the contract is sent to a signer. |
Watch Contract Signed |
Triggered when all signers have signed the contract. |
Watch Contract Signed By A Signer |
Triggered when each individual signer has signed the contract. |
Watch Webhook ErrorService is unavailable due to a failure, a service responds with unexpected data or the validation of input data fails. More Notifications |
Triggered when an error has occurred (eg. delivery issue). |
Creates a new contract.
Connection |
||
Test Mode |
Choose between sending a Live contract or a Test contract. |
|
TemplateTemplates are predefined scenarios that you can expand and customize to create new scenarios. You can then share these with friends and colleagues. More |
Select the template you want to use for the contract. |
|
Placeholder fields |
Specify Placeholders in the template to be replaced with your custom data. |
|
Signers |
API key |
this is a Placeholder name as specified in the template editor. |
Value |
data that would replace the Placeholder. |
|
Add and specify signers of the contract. |
||
Name |
name of the signer. |
|
|
email address of the signer (for identification). |
|
Mobile |
mobile number of the signer (for identification). |
|
Ticking the box beside Show advanced settings in the Signer field allows you to add. |
||
Company Name |
company name of the signer. |
|
Redirect URL |
the URL that the signer will be redirected to after signing the. contract. |
|
Auto Sign |
enable this option to automatically add the signer’s signature to the contract. |
|
Signing Order |
to specify the order of signers. When the same number is used for two or more signers, they will receive the signature request at the same time. |
|
(Advanced settings) Contract Title |
Enter the unique title of the contract (the template name is used when not specified). It appears in emails, generated documents, and dashboard pages. |
|
(Advanced settings) Metadata |
Add your own custom information (eg. your own recordOne row in the Boost.space database. These are individual rows under spaces in each module. For example single products, but not their variants. More ID). |
|
(Advanced settings) Language |
Select the signer page/email language. |