Agreement Actions

Agreement actions are Docshark's contract automation: when something happens to an agreement, typically a signature completing, Docshark performs the next step itself.

What actions can do

The core action: create a downstream envelope from a template. When the trigger fires:

1. The named template is instantiated.
2. Placeholders fill from the source agreement's own field values. The client's name, company, and terms carry straight into the next document.
3. The new envelope is created (and sent, depending on configuration) to the mapped recipients.

The classic chain: a signed order form automatically produces the onboarding agreement, with the customer's details already inside, and signing continues without anyone touching a keyboard.

Triggers

Actions hang off envelope lifecycle events. The same events that drive webhooks: completion is the common trigger (signed → next step), with the others available for notification-style automation.

Field-to-placeholder mapping

The mapping is the setup that makes it work: each placeholder in the downstream template maps to a field or placeholder value on the source agreement. Configure it once. Every triggered envelope arrives pre-filled, and mismatched or missing values surface at creation rather than reaching the signer blank.

What stays on the record

• The trigger event and the envelope it produced are linked. The child envelope's record shows which agreement spawned it.
• Failures (missing required data, send-limit headroom) surface as action errors, not silent skips. Check your plan's send limit before wiring high-volume chains.

Building a chain

Keep chains legible: order form → onboarding agreement → welcome packet is three hops anyone can follow. The moment a chain needs "if signed on a Tuesday," do it in your own systems via webhooks. Actions are for the straight lines every contract repeats.