Make an app’s records a source of Work
Many organizations start a piece of Work somewhere else: a won deal in HubSpot, a new project in Jira. Make that app a source of Work and each of those records is linked to the Work it belongs to, without anyone linking them by hand. You then see, on every piece of Work, the records behind it.
Add a source with a ready-made setup
A ready-made setup does three things in one go: it adds the app’s records as a type, with what they mean already written, links that type to Work, and switches on the Common work attribution agent for it.
It’s offered for the records where Work usually starts in each app:
| App | Records |
|---|---|
| HubSpot | Deals |
| Attio | Deals |
| Jira Cloud | Projects |
| Linear | Projects |
Everything beneath one of these, such as a project’s issues, belongs to the same Work.
You need Manage types and links, Manage actions and Update Entity Configuration, because the setup adds a type, a link and an action that changes Work. Ask your Flowstate admin.
- Connect the app if you haven’t already.
- Go to Organization → Modules → Ontology platform and select Add type.
- Under From an app you’ve connected, select the connection.
- Tick the kind of record, such as Deals.
- Leave Link each record to its Work ticked. It shows once you tick a kind where Work starts in that app.
- Select Add 1 type.
From then on, each new or changed record is read by the agent and linked to the Work it belongs to. When no Work fits, the agent adds one. You follow each run on the Runs tab, like any action. See Follow a run.
To add the records without linking them to Work, untick Link each record to its Work. You can link them yourself later.
See where your Work comes from
Go to Work and open the Sources tab. Each row is one kind of record from one place, such as the deals from your HubSpot connection, with:
- Linked records: how many of its records are linked to Work.
- Work items: how many pieces of Work they’re linked to.
Search the list by the connection, the app or the kind of record.
When there’s nothing here yet, someone with Manage types and links, in an organization with the Ontology platform, sees Add your first source and an Add a source button that opens the Types tab. Everyone else sees Ask an administrator to add a source.
See the records behind a piece of Work
- On the Work list, the Sources column shows an icon for each place a piece of Work’s records come from. Hover over one to see how many records are linked. When it’s a single record, select the icon to open it in its app.
- On a piece of Work’s own page, Sources lists each linked record on its own line. A record with an arrow opens in its app.
Show Work values in the Work list
A Work value is any Currency or Text property on Work, such as a deal’s amount or a client code. You add one on the Work type, and an action can fill it in.
- On the Work list, open Display.
- Pick the values you want as columns.
None shows until someone picks it, and an export carries the columns shown. A piece of Work’s own page shows its values under Sources.
To see money values, such as an amount, you need access to Work money. Ask your Flowstate admin.
If something’s not right
A kind says “Added, not linked to Work yet”. It was added as a type, but its link to Work and its agent weren’t. Tick it again with Link each record to its Work ticked, and select Add 1 type.
You don’t see Link each record to its Work. It’s offered only for the records in the table above. For other records, add a link and an action yourself.
You can’t add the setup. You need Manage types and links, Manage actions and Update Entity Configuration. See Who can do what.
A money value doesn’t show in Display. You need access to Work money.