Integrations

Reference external content directly in your prompts. Instead of copying and pasting, mention a Slack thread, Notion page, or ticket ID, and the agent pulls the content automatically.

Available integrations

Integration	What you can reference
Slack	Messages and threads
Notion	Pages and databases
Linear	Issues, descriptions, and comments
Jira	Issues, descriptions, and comments
Confluence	Pages and spaces
Google Docs	Documents

Connect an integration

1. Go to Settings > Integrations in your EkLine dashboard
2. Find the integration you want to connect
3. Click Connect and allow access in the popup.
4. The integration is now available in all Docs Agent sessions.

Each team member connects their own account. The agent can only access content you have permission to view.

Slack

Turn support conversations, incident threads, and team discussions into structured documentation.

Use cases:

• Convert a support answer into a how-to guide.
• Document troubleshooting steps from an incident channel.
• Create FAQ entries from common customer questions.

Example:

Create a troubleshooting guide based on this Slack thread:
https://workspace.slack.com/archives/C01234/p1234567890

The agent extracts the conversation, identifies the problem discussed, and structures it into documentation format.

Notion

Pull product specs, design documents, and meeting notes into your documentation workflow.

Use cases:

• Transform product specs into technical documentation.
• Create user guides from design documents.
• Generate API docs from specification pages.

Example:

Create API documentation based on the spec in this Notion page:
https://notion.so/your-workspace/api-spec-page-id

Linear

Reference completed work to update documentation or generate release notes.

Use cases:

• Update docs when a feature ships.
• Generate release notes from a milestone.
• Create changelog entries from issue descriptions.

Examples:

Update the authentication docs based on Linear ticket ENG-1234.

Generate release notes for all issues in the v2.0 milestone.

The agent reads the issue title, description, and comments to understand what changed.

Jira

Reference Jira issues the same way you reference Linear tickets.

Use cases:

• Update documentation based on completed stories.
• Generate release notes from a sprint or version.
• Create technical specs from epic descriptions.

Example:

Update the deployment guide based on Jira ticket PROJ-5678.
Include the new configuration options mentioned in the ticket.

Confluence

Pull existing documentation, runbooks, and internal knowledge into new docs.

Use cases:

• Migrate internal docs to your public documentation.
• Create user guides from technical runbooks.
• Reference architecture decisions in new documentation.

Example:

Create a public deployment guide based on the internal runbook:
https://your-org.atlassian.net/wiki/spaces/ENG/pages/123456

Google Docs

Reference Google Docs for content that lives outside your other tools.

Use cases:

• Transform PRDs into technical documentation.
• Create guides from proposal documents.
• Pull content from collaborative drafts.

Example:

Create a feature overview based on the PRD in this Google Doc:
https://docs.google.com/document/d/abc123/edit

Combine multiple sources

Reference multiple integrations in a single prompt to create comprehensive documentation.

Update the authentication docs based on:
- Linear ticket ENG-1234 (the feature implementation)
- This Slack thread where we discussed edge cases:
  https://workspace.slack.com/archives/C01234/p1234567890
- The original spec in Notion:
  https://notion.so/your-workspace/auth-spec

Tips

Best practices

• Reference exact URLs or IDs — The agent doesn’t search; it needs direct references.
• Verify access — You can only pull content you have permission to view.
• Add context — Tell the agent what kind of documentation you need from the source.
• Combine thoughtfully — Multiple sources work best when they relate to the same topic.