getsign_create_workflow
Create a Getsign workflow for a Monday board, optionally from templates.
THIS IS THE DEFAULT WAY TO CREATE A WORKFLOW. A workflow (envelope) is
board-scoped, so creating one needs only board_id and workflow_name — no
item.
workflow_name is REQUIRED — ask the user what to call the workflow before
calling this, and do not invent a name on their behalf. The backend has no
name fallback: creating without one produces an envelope literally named
"undefined (Copy)" on the board. The name is user-visible on the monday
board, so prompt for something recognizable — usually the source document
or the kind of agreement (e.g. "NDA - Acme Corp"). Calling with a blank or
whitespace-only name returns MISSING_WORKFLOW_NAME instead of creating
anything.
A new workflow inherits the account's email configuration (sender
identity, message, reminders, logo, OTP) and security settings by
default. Ask the user whether to inherit those from the account or
override them with workflow-specific ones, and pass the answers as
inherit_account_email_configuration / inherit_account_security_settings
(True = inherit, False = override with this workflow's own values). Leave
them unset to keep the account-inheriting default. Overriding email
config is what lets a workflow have its own logo/sender that don't track
later account changes.
The response carries a display_summary (the same curated four-section
view as getsign_get_workflow). Present that summary — section titles +
descriptions + current values — rather than the raw settings blob, and
only expand a section's details when the user asks about it.
The response also carries post_create_questions — ALWAYS ask both of
its questions right after creation, before attaching a document or
mapping fields: (1) template workflow vs. Use stored document for
where the signing document comes from, and (2) whether to enable any
of the optional features (Generate document, Signature collection,
Share and track). Explain each option using the given descriptions.
Asking is mandatory — enabling or choosing anything is not. A "decide
later" answer is fine, don't block on it, and never flip a toggle on
without an explicit yes.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| board_id | Yes | ||
| workflow_name | Yes | ||
| template_gallery_ids | No | ||
| inherit_account_security_settings | No | ||
| inherit_account_email_configuration | No |