Delivery methods

The signed documents from a SmartFlow can be delivered a number of ways. It can be delivered automatically through an integration or API, it can be fetched manually from the activity log or it can be delivered through one of the four ways that can be configured from directly within the delivery method node of the SmartFlow designer:

  1. Email to signee
  2. Email to sender
  3. Email to email inbox
  4. Deliver by webhook

This article will cover the four methods that are configurable from within the SmartFlow. For instructions on delivering SmartFlow documents through an integration click here, and for instructions on fetching documents manually from the activity log click here.

Add delivery method

To add a delivery method click the "+ Delivery method" button in the SmartFlow Designer.

Next click the desired delivery method to add and configure it.

Email to signee

This delivery method sends a conformation email to the signee of the SmartFlow. 

Here you can edit the title and body of the email. You can reference items that have already been associated with the SmartFlow process, such as information about the signee (name of the signee, their National ID number (if qualified signature), their email address and phone number) or information from the SmartFlow (the name of the SmartFlow and the name of Your Company).

To use these references simply click at the appropriate place in the email that you would like the reference to appear, and click the reference icon in the top banner.

The first line in the email editor is both the subject of the email, and the title in the email body (shown in bold.

The signed document is delivered as an attachment by default but this can be changed by unchecking the "include signed document in attachments" checkbox. 

Email to sender

This delivery method sends a notification email to the person that sent the SmartFlow to the signee. If the SmartFlow is initiated directly from the signee, this delivery method will not send any email.

Here you can edit the title and body of the email. You can reference items that have already been associated with the SmartFlow process, such as information about the signee (name of the signee, their National ID number (if qualified signature), their email address and phone number) or information from the SmartFlow (the name of the SmartFlow and the name of Your Company).

To use these references simply click at the appropriate place in the email that you would like the reference to appear, and click the reference icon in the top banner.

The first line in the email editor is both the subject of the email, and the title in the email body (shown in bold.

The signed document is delivered as an attachment by default but this can be changed by unchecking the "include signed document in attachments" checkbox. 

Email to email inbox

This delivery method sends a notification email to one or more specific email addresses. Typically this will be a central email address such as department@yourcompany.com. When only emails are configured as delivery methods we highly recommend using this delivery method since it assures that all documents are delivered to one central location. 

Here you can edit the title and body of the email. You can reference items that have already been associated with the SmartFlow process, such as information about the signee (name of the signee, their National ID number (if qualified signature), their email address and phone number) or information from the SmartFlow (the name of the SmartFlow and the name of Your Company).

To use these references simply click at the appropriate place in the email that you would like the reference to appear, and click the reference icon in the top banner.

The first line in the email editor is both the subject of the email, and the title in the email body (shown in bold.

The signed document is delivered as an attachment by default but this can be changed by unchecking the "include signed document in attachments" checkbox. 

Delivered to external system with webhooks

Webhooks are a way of sending signed documents directly to an external system. It requires the company to configure the receiving system to accept the webhooks.

Taktikal will send a POST request to the registered URL when an event occurs with information that confirms that Taktikal is the sender of the documents. The request includes information about the signee along with the document as a Base 64 string and attachment references when applicable.

Available events are:

  1. All signed (triggered when the final signee has signed the document)
  2. Signed document (triggered when any signee except the final signee has signed the document)
  3. Created (triggered when a new signing process is created)
  4. Canceled (triggered when a signing process is canceled)
  5. Expired (each signing process needs to be signed within 30 days. If it expires this event will be triggered. If any signees have signed the document prior to expiration the document will be delivered with those signatures.)

If webhooks are the main delivery method we recommend choosing the trigger "All signed" and expired to ensure that all signed documents are delivered. All other triggers are optional.

See technical documentation for webhooks.

Next: Integrations ➜ (coming soon)

Articles in this section