ShrubberyDocs
Sign in

URL Drop

Definition

The capture path where the Lead pastes a URL from an external tracker (Jira, Linear, GitHub) and Shrubbery creates a linked Draft Shrubbery without AI involvement.

Avoid: link paste, issue import, URL import.

Role

URL Drop is the structured, no-AI capture path for commitments that already exist in an external system. The Lead pastes a tracker URL; the server parses the host and extracts the external ID, then creates a Draft row with source = url_drop and the (external_system, external_id) pair stored for deduplication and sync.

No AI extraction happens — the objective, assignee, and deadline fields are pre-filled from the URL metadata where available and presented for the Lead to review and complete. The resulting row is idempotent on (external_system, external_id, assigner): two Leads may independently track the same Jira ticket without collision.

If the URL host is unrecognised, the path falls back to a Manual Contract form pre-filled with the URL as the source excerpt. No external mapping is persisted in that case.

Lifecycle

Not a stateful concept — URL Drop is a capture path, not an entity. It produces a Draft row and exits.

  1. Lead pastes a Jira / Linear / GitHub URL.
  2. Server parses host and external ID → Draft row created with source = url_drop and (external_system, external_id) stored.
  3. Lead reviews fields and saves.
  4. Lead promotes to Pending_Handshake from the Detail Sheet when ready.

Last updated: 22 June 2026