Skip to main content
Use this page when you want to turn a Custory item into delivery work in another tool and keep the link visible inside the journey.

​
What this feature does

A linked task connects one Custory item to one external work record. Custory stores the link on the item, keeps a cached title and status, and saves a direct URL back to the external issue or page. When you create the task from Custory, the external record also includes a link back to the source item.

​
Supported platforms

​
Before you create a linked task

You need:
  • an existing item
  • an active integration for the target platform
  • Editor or Owner access in the journey or workspace
Viewers can review linked tasks, but they cannot create, edit, or remove them. If the integration is expired or error, Custory blocks task creation until the connection is fixed.

​
Create a linked task

  1. Open the item you want to hand off.
  2. Choose the target platform.
  3. Select the destination, such as a repository, project, team, or database.
  4. Review the title and description, or use AI fill if you want Custory to draft them from the item.
  5. Create the task.
Custory sends the title or summary to the external tool and appends a link back to the source item.
Custory external task creation dialog in light mode

​
Journey defaults

Journey settings can preselect the usual destination for each platform: These defaults only prefill the create form. You can still choose a different destination when you create a specific task. Each linked task record in Custory stores:
  • platform
  • external ID
  • external key when the tool has one, such as PROJ-123 or TEAM-45
  • external URL
  • cached title
  • cached status
  • creation time
  • last sync time when a sync has run
This is what lets the item show delivery progress without becoming the delivery tool itself.

​
Sync and editing behavior

Custory runs linked-task status sync across all four supported platforms. When you open task details from Custory, it fetches the current external record for that platform. The external tool remains the source of execution. Custory only removes its own link record.

​
When to use this page vs other pages

  • Use GitHub integration for GitHub-specific repository behavior, PR workflows, and GitHub-triggered automations.
  • Use Journey settings to set per-journey defaults for repositories, projects, teams, or databases.
  • Use Automations if you want issue creation to happen automatically for GitHub, Jira, or Linear.

​
Next step

Read Item details and fields if you need to strengthen the item before handoff, or GitHub integration if the delivery workflow depends on repositories, pull requests, or GitHub automations.