Connect Linear to ECA
Give ECA governed access to Linear’s 82 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Linear to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Linear in Runlayer
Add Linear from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Linear’s 82 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Linear
Sign in the way Linear requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Linear from ECA
Linear’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
82 Linear tools in ECA
Runlayer policy decides which of these ECA users can call. 17 read data only.
Create attachment
Deprecated fallback for tiny files only.
Create attachment from upload
Link an already-uploaded Linear assetUrl to an existing issue as an attachment.
Create initiative label
Create a new Linear initiative label.
Create issue label
Create a new Linear issue label.
Delete attachment
Delete an attachment by ID
Delete comment
Delete a Linear comment.
Delete customer
Delete a customer in Linear
Delete customer need
Archive a customer need in Linear
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Linear call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more