Mankomail

MyNotary — event ​

Starts the workflow when MyNotary reports an event: a completed signature, a new case, a registered notification. The body lands in data.mynotary.

The MyNotary — event trigger starts the workflow when MyNotary reports an event on the workflow's URL: a completed signature, a new case, registered letters sent. The event that matters most is signature_completed ("Signature completed"): it is when MyNotary delivers the signed documents.

The URL is the workflow URL, the same as for Webhook received: <PUBLIC_BASE_URL>/hooks/wf/<token>. It is issued on the first publication of the workflow and returned only once; POST /api/v1/workflows/<id>/webhook issues a new one (the previous one stops working). The subscription on the MyNotary side is created by API, with the "Webhook" resource of the MyNotary node ("Create a webhook" operation, "Callback URL" field): no MyNotary screen to open. The same node lists and deletes subscriptions.

The run has no triggering email: nodes that act on the triggering email (reply in the thread, Move, Flag) cannot be used after this trigger, and the editor reports them as a blocking error. Send still works when you choose the sending mailbox on the node.

At a glance ​

  • Type: trigger.mynotary · version 1
  • Category: Triggers
  • Kind: Trigger — starts a run
  • Effect: No external effect (none) — nothing is written outside Mankomail; safe to replay
  • Needs a carrier email: No
  • Connection: MyNotary
  • Outputs: main

Connection ​

This node needs a MyNotary connection.

Parameters ​

connection ​

MyNotary connection — The MyNotary connection to use. Create it once in Connections; its key never appears in the workflow.

  • Type: Connection (credential)
  • Required: Yes
  • Default: "" (empty)

events ​

Events — What starts this workflow. Nothing ticked = everything MyNotary sends, that is the events of all your firms.

  • Type: Several choices (multiOptions)
  • Required: No
  • Default: ["signature_completed"]
  • Options:
    • signature_completed — Signature completed
    • signature_created — Signature started
    • signature_cancel — Signature cancelled
    • contract_created — Contract created
    • contract_deleted — Contract deleted
    • operation_created — Case created
    • operation_deleted — Case deleted
    • operation_merged — Cases merged
    • legal_record_deleted — Record deleted
    • register_letter_created — Registered letters sent
    • register_letter_cancel — Registered letters cancelled
    • register_letter_completed — Registered letters completed

organization ​

Firm concerned — Informational: MyNotary sends every firm’s events to the same URL. To handle one firm only, compare data.mynotary.organizationId in a condition.

  • Type: Remote resource (resourceLocator)
  • Required: No
  • Ways to choose: pick from a list, type an ID (mynotary.organization)
  • Listed with the connection in: connection

Outputs ​

  • main — Taken by every run started by a MyNotary event that passed the event filter.

Data produced ​

What this node adds to the run data, and how to read it in an expression. <step> stands for the step key: the node name turned into an identifier (see Data and expressions).

  • {{ data.mynotary }} — object. The JSON body of the event, exactly as MyNotary sent it.
  • {{ data.mynotary.eventId }} — string. The event type, e.g. signature_completed. Despite its name, it is not a delivery identifier.
  • {{ data.mynotary.organizationId }} — number. The firm the event belongs to. Compare it in a Condition to handle a single firm.
  • {{ data.mynotary.contractId }} — number or string. The contract concerned, for contract and signature events. Pass it to the MyNotary node to read the contract.
  • {{ data.mynotary.files.0.signedFileId }} — string. On signature_completed: identifier of the first signed file, to download with the MyNotary node.

Example ​

File every signed mandate. Add a MyNotary — event trigger with events set to "Signature completed" (the default). Publish, then create the subscription once with a MyNotary node: resource "Webhook", operation "Create a webhook", "Callback URL" set to the workflow URL.

When a signature completes, a run starts on the main port. A MyNotary node downstream reads the contract with {{ data.mynotary.contractId }} and downloads {{ data.mynotary.files.0.signedFileId }}.

Tips ​

  • MyNotary sends everything. Every event of every firm attached to the API key arrives on the same URL. The trigger keeps only the ticked events and drops the others before any run exists; nothing ticked means every event. "Firm concerned" is informational only: to handle a single firm, compare {{ data.mynotary.organizationId }} in a Condition.
  • Proof of origin. MyNotary does not sign its bodies: the token in the URL is the only proof. Keep the URL secret.
  • No deduplication. MyNotary sends no delivery identifier, so a delivery sent twice starts two runs. A workflow that writes elsewhere should protect itself (a table of processed contracts, a condition on a status).
  • Missed events. If a delivery may have been lost, a Schedule workflow that queries MyNotary with the MyNotary node catches up on what the webhook missed.
  • Responses. 202 with { "executionId" } when a run is created, 202 with no body when the event is not one you ticked, 404 when the token is unknown or the workflow is not published. The other rules of the URL (POST only, JSON body up to 256 KB, 300 calls per minute per IP) are those of Webhook received.
  • A workflow has at most one MyNotary — event trigger, and only the published version receives events.