Ironclad · Arazzo Workflow

Ironclad Schedule a Signature Send

Version 1.0.0

Read sign status, schedule the signature request for a future time, then re-read the workflow.

1 workflow 1 source API 1 provider
View Spec View on GitHub Contract Lifecycle ManagementCLMContractsLegal TechLegalOpsEnterpriseWorkflowsE-SignatureClickwrapArtificial IntelligenceAuthenticationSCIMWebhookArazzoWorkflows

Provider

ironclad

Workflows

schedule-signature-send
Check sign status, schedule the signature send, then retrieve the workflow.
Retrieves the sign status, schedules the signature request for a future timestamp, and retrieves the workflow.
3 steps inputs: authorization, notifyAt, reminderDaysBefore, workflowId outputs: scheduledStatus, signStatus, step
1
getSignStatus
Retrieve the sign status to confirm the workflow is on the Sign step and not yet out for signature.
2
scheduleSend
Schedule the signature request to be sent at the supplied notify-at timestamp, with an optional reminder.
3
retrieveWorkflow
Retrieve the workflow to confirm its state after scheduling the send.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Ironclad Schedule a Signature Send
  summary: Read sign status, schedule the signature request for a future time, then re-read the workflow.
  description: >-
    Schedules a signature request to go out at a future time for a workflow on
    the Sign step. The flow reads the sign status to confirm the workflow is on
    the Sign step and not yet out for signature, schedules the signature request
    for a supplied notify-at timestamp, and retrieves the workflow to confirm
    its state. Each step inlines its request so the chain can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: workflowsApi
  url: ../openapi/ironclad-workflows-api-openapi.yml
  type: openapi
workflows:
- workflowId: schedule-signature-send
  summary: Check sign status, schedule the signature send, then retrieve the workflow.
  description: >-
    Retrieves the sign status, schedules the signature request for a future
    timestamp, and retrieves the workflow.
  inputs:
    type: object
    required:
    - authorization
    - workflowId
    - notifyAt
    properties:
      authorization:
        type: string
        description: Bearer token for the Ironclad Authorization header.
      workflowId:
        type: string
        description: The unique identifier or Ironclad ID of the workflow on the Sign step.
      notifyAt:
        type: string
        description: ISO8601 timestamp for when the signature request should be sent.
      reminderDaysBefore:
        type: integer
        description: Optional number of days before the scheduled send to email a reminder (1-7).
  steps:
  - stepId: getSignStatus
    description: >-
      Retrieve the sign status to confirm the workflow is on the Sign step and
      not yet out for signature.
    operationId: get-sign-status
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authorization
    - name: id
      in: path
      value: $inputs.workflowId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      signStatus: $response.body
  - stepId: scheduleSend
    description: >-
      Schedule the signature request to be sent at the supplied notify-at
      timestamp, with an optional reminder.
    operationId: schedule-send-signature-request
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authorization
    - name: id
      in: path
      value: $inputs.workflowId
    requestBody:
      contentType: application/json
      payload:
        notifyAt: $inputs.notifyAt
        reminder:
          daysBefore: $inputs.reminderDaysBefore
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      scheduledStatus: $response.body
  - stepId: retrieveWorkflow
    description: >-
      Retrieve the workflow to confirm its state after scheduling the send.
    operationId: retrieve-a-workflow
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authorization
    - name: id
      in: path
      value: $inputs.workflowId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      step: $response.body#/step
  outputs:
    signStatus: $steps.getSignStatus.outputs.signStatus
    scheduledStatus: $steps.scheduleSend.outputs.scheduledStatus
    step: $steps.retrieveWorkflow.outputs.step

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/ironclad-schedule-signature-send"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.