How do I connect Linear to a decision flow?
Add Linear as a connection in your workspace authenticating with an API key or OAuth 2.0, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Linear in a decision without ever seeing the secret.
Can I test Linear without touching production?
Linear exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.
What can a flow call on Linear?
8 operations, including “Verify connection”, “Create an issue”, “Get an issue”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Verify connection”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.
Where in a decision should Linear be called?
Operational work begins where the decision ends. Creating an issue, adding its evidence and keeping its state current from the flow gives the team one durable record of what was decided and what must happen next, without a second copy drifting in a handoff.
