MyNotary

Your cases, records, contracts and signed documents — to file an emailed document, create a case or react to a signature.

A MyNotary connection lets the MyNotary node work with the cases, records, contracts and documents of the firms linked to your application: file an emailed document into a case drive, create a case or a record, create a contract from a model, track a signature. The same connection feeds the MyNotary — event trigger, which starts a workflow when MyNotary reports an event such as a completed signature.

The connection holds a MyNotary application key and an environment. The key is encrypted at rest, applied by the server at call time as the x-api-key header, and never appears in a workflow.

At a glance

• Identifier: mynotary
• Family: Service
• Set up by: A member (personal) or an administrator (shared with the organisation)
• Authentication: API key or token
• Credential type: service:mynotary
• Official API documentation: https://dev.mynotary.fr
• Environments: Pre-production (preprod) — https://api-preprod.mynotary.fr/api/v1 ; Production (production) — https://api.mynotary.fr/api/v1
• Rate limit applied by Mankomail: 300 requests per minute and per connection; up to 3 attempts on a 429 or a 5xx
• Connection test: Yes

Step by step

The same steps are shown in the connection form of the app.

1. Ask MyNotary (support@mynotary.fr) for your application key: one for pre-production, one for production. It is not self-served.
2. Pick the environment below: a pre-production key does not work in production, and the other way round.
3. On the firm’s side (PREMIUM plan required), an administrator opens “Account settings → Interconnections” and copies their organization key.
4. That organization key is exchanged ONCE for an id, through POST /clients: it is never stored and is not asked for here.
5. Test the connection: the firms already linked to your key are listed, and the node will offer them in a picker.

Connection fields

Field	Kind	Required	Notes
Environment (environment)	Choice	Yes	Pre-production is a sandbox: nothing signed there has any legal value. preprod (Pre-production (sandbox)), production (Production) Default: production
Application key (apiKey)	Secret — never shown again	Yes	Sent as the x-api-key header. It grants access to EVERY firm linked to your application.

Before you start

• The application key is not self-served. Ask MyNotary support for it (the in-app guide gives the address). You get one key for pre-production and one for production; neither works in the other environment.
• On the firm’s side, a PREMIUM subscription is required. An administrator of the firm opens Account settings → Interconnections and copies the organisation key.
• The organisation key is exchanged once, through MyNotary’s POST /clients, for an organisation id linked to your application. Mankomail does not perform this exchange and never stores the organisation key: do it once, following MyNotary’s developer documentation. Once linked, the firm appears in the node’s firm picker.
• The application key gives access to every firm linked to your application. Use an Organisation connection only if every member of the organisation may act on all those firms.
• MyNotary’s API cannot send a contract for signature: sending is done in the MyNotary interface. A workflow prepares the case, the records and the contract; a person sends it; the trigger reacts to the signature.

Permissions

MyNotary has no scopes: the application key can do everything the API allows, for every linked firm. Almost every call needs the firm’s id, which is why the firm is the root of every picker in the editor:

Picker	Depends on
Firm	— (the firms linked to the key)
User, Case type, Case	Firm
Contract model	Firm → Case type (a contract model only exists inside a case type)
Record type	—

The node offers six resources: Case (list, get, create, add a party), Contract (list a case’s contracts, get, create from a model, track the signature), Record (search, get, create, update), Document (list a case drive, get a download link, download, upload), User (list) and Webhook (list, create, delete). MyNotary offers no idempotency key: replaying a creation step after an incident creates a second record or case, so search before you create.

Every call also sends x-api-documents-version: 2, so that document fields hold file ids rather than download URLs.

Environments

The connection carries the environment, never the node: Pre-production (sandbox) or Production. Nothing signed in pre-production has legal value.

• The form proposes Production by default; check it before saving.
• If the stored value is missing or unknown, the connection falls back to the first declared environment, pre-production: a damaged connection leads to the less risky side.
• Each environment needs its own key. To work in both, create two connections (for example “MyNotary — pre-production” and “MyNotary — production”); the environment shows as a badge on each connection. Changing the environment of an existing connection without re-entering the key is not saved: create a new connection instead.

Add the connection

1. Open Connections. In the Third-party services section, find the MyNotary card and click Connect.
2. Give the connection a Name, choose the Scope — Personal (only you) or Organisation (the whole organisation; only an administrator can create one) — then the Environment.
3. Paste the Application key and click Create the connection.
4. Back in the list, click Configure on the new connection, then Test the connection.

The test calls GET /organizations. It shows The connection works followed by the first linked firm and the number of others (“Firm name +2”). A valid key with no linked firm yet passes the test without a name: link a firm through the organisation key exchange before building a workflow.

In a node, pick the connection in MyNotary connection, then the firm, then the lists that depend on it. Delete is refused while a published workflow uses the connection.

Webhooks

The MyNotary — event trigger receives MyNotary’s webhooks on the workflow’s URL:

<PUBLIC_BASE_URL>/hooks/wf/<token>

• Getting the URL. The token is generated at the workflow’s first publication and returned only once; only its fingerprint is kept. You can generate a new one with POST /api/v1/workflows/{id}/webhook (see the API): the response gives webhook.url (/hooks/wf/<token>), to prefix with <PUBLIC_BASE_URL>. Generating a new URL invalidates the previous one.
• Subscribing. MyNotary subscriptions are managed through the API: use the MyNotary node, resource Webhook, operation Create a webhook, with the URL in Callback URL. The subscription is created with authType: NONE. Delete a webhook removes it.
• Proof of origin. MyNotary signs nothing. The only proof is the 256-bit token in the URL. Keep the URL private, and regenerate it if it leaks.
• Filtering. MyNotary sends every event of every firm linked to the key to the same URL. Mankomail reads eventId in the body and creates a run only if it is one of the Events ticked on the trigger (default: Signature completed). Nothing ticked means every event. A filtered-out event is acknowledged with 202 and creates nothing. The Firm concerned field is informational: to handle one firm only, compare data.mynotary.organizationId in a condition.
• No deduplication. eventId names the event type, not the delivery: MyNotary provides no delivery id. A delivery replayed by MyNotary creates a second run. Workflows that write elsewhere must protect themselves (a lookup table, a status check).
• Responses. 202 with an executionId when a run starts; 202 without a body for an ignored event; 404 for an unknown token or an unpublished workflow; 400 if the body is not JSON; 413 above 256 KB; 429 above 300 calls per minute from the same IP.

The body arrives under data.mynotary (for example {{ data.mynotary.contractId }}). The run has no triggering email. Since MyNotary documents no retry policy, a polling fallback (a Schedule trigger with Track the signature) catches what a lost webhook would miss.

Common errors

Message or code	Cause	What to do
Test: “the service rejects the key” (integration.unauthorized)	Wrong key, or a key from the other environment.	Check the Environment; if the key is for the other one, create a new connection with the right environment.
Test passes with no firm name	The key is valid but no firm is linked yet.	Exchange the firm’s organisation key (POST /clients), then test again.
Test: “the service quota is exceeded” (integration.rate_limited)	MyNotary answered 429.	The key is fine: try again in a moment.
integration.unauthorized during a run	401 or 403.	Replace the key, or check that the firm is still linked to your application.
integration.not_found	404: the case, contract, record or file does not exist in this firm or this environment.	Check the ids and the connection’s environment.
integration.rejected	400 or 422: MyNotary refused the body (for example a contract model that does not belong to the case type).	Fix the node settings.
integration.rate_limited	429 after retries. Mankomail sends at most 300 requests per minute per connection and retries up to 3 times, honouring Retry-After.	Transient: the engine resumes the step later.
integration.unavailable	5xx, 409 or network failure, after retries.	Transient: the engine resumes the step later.
integration.connection_unusable	The connection was deleted, is not active, is out of your scope, or belongs to another service.	Pick a valid connection in the node.
The trigger never fires	The workflow is not published, the subscription points to an old URL, or the event is not ticked.	Publish, check List webhooks, regenerate the URL if needed, and review Events.

Webhook events

The events offered by the trigger. An event the provider adds later is still accepted when no event is ticked.

Event	Label
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

Nodes that use this connection

• MyNotary — event — trigger.mynotary
• MyNotary — mynotary.api