Features

Patch the tools you already use into the task.

GitHub sends work in. Slack and Google Calendar carry it out. Every cable is scoped by whoever owns that end, and nobody copies updates across by hand.

  • GitHubPR #214 · open
  • Slackposts to #delivery
  • Google Calendardue Fri 19 Sep
  • CSV142 tasks imported

VEY-214 In review

Empty states for the mobile task list

  • GitHub
  • Slack
  • Google Calendar
  • CSV

One cable at a time

Each connection is scoped by whoever owns that end.

GitHub, attached to the task

Install the GitHub App and choose, on GitHub, which repositories Veyrd may see. From then on an issue or pull request can be attached to a task and read in place.

  • Pick repositories, issues and pull requests from inside Veyrd
  • See a linked item's title and status on the task
  • Repository access stays under your control on GitHub

Slack, only where you want it

Connect the workspace, pick a channel, and turn on the event types worth interrupting people for.

  • Task created, task updated, task deleted and new comments
  • One channel per workspace installation, changeable at any time
  • Connecting and changing the channel is an admin action

Calendar, per person

A calendar connection belongs to the member who made it, not to the workspace. Each member decides how much of the workspace reaches their week.

  • Only the tasks assigned to you, or every task in the workspace
  • Completed work can stay on the calendar, marked done
  • Sync health, a manual resync, and disconnect at any time

Bring work in, take it out

A spreadsheet is a perfectly good starting point.

Import a CSV into the project you choose, and export whatever a view is currently showing. Nothing you put in is trapped.

CSV import into a chosen project CSV export of the tasks a view is showing

Early access

Open a workspace. Write the first line.

We’re opening Veyrd to teams in waves. Join the waitlist and we’ll email you when your workspace is ready.

See pricing