feat(integrations): add AgentLine provider by Sameersribot · Pull Request #6700 · NangoHQ/nango

Sameersribot · 2026-07-06T17:47:04Z

What

Adds AgentLine as a new integration provider.

AgentLine is the voice infrastructure for AI agents — phone numbers, calls, and SMS through a single API.

Provider config

auth_mode: API_KEY (Bearer token)
base_url: https://api.agentline.cloud
verification: GET /v1/agents
categories: communication

Changes

Added agentline entry to packages/providers/providers.yaml (alphabetically before agiloft)
Created docs/api-integrations/agentline/connect.mdx with setup guide
Added AgentLine logo (docs/api-integrations/agentline/account.png)
Entry in docs/docs.json alphabetically sorted

Add AgentLine as a new API_KEY provider: - providers.yaml: agentline entry with communication category - docs: connect.mdx setup guide and account.png logo - docs.json: alphabetical entry in api-integrations

Copilot

Pull request overview

Adds AgentLine as a new API integration provider, including provider configuration and initial documentation so users can connect via an API key.

Changes:

Added an agentline provider entry to packages/providers/providers.yaml (API key auth + proxy verification).
Added a connection setup guide at docs/api-integrations/agentline/connect.mdx (with screenshot).
Added api-integrations/agentline to docs/docs.json for docs routing/navigation.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 5 comments.

File	Description
packages/providers/providers.yaml	Introduces the AgentLine provider config (auth, proxy base URL, verification endpoint, docs links, credential schema).
docs/docs.json	Registers the AgentLine docs route in the docs index/navigation list.
docs/api-integrations/agentline/connect.mdx	Adds a “Connect” setup guide describing how to obtain and enter an AgentLine API key.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+    proxy:
+        base_url: https://api.agentline.cloud
+        headers:
+            authorization: Bearer ***


+    docs: https://nango.dev/docs/api-integrations/agentline
+    docs_connect: https://nango.dev/docs/api-integrations/agentline/connect


              "api-integrations/agiloft",
              "api-integrations/agiloft-cc",
+              "api-integrations/agentline",
              "integrations/all/aimfox",


              "integrations/all/affinity-v2",
              "api-integrations/agiloft",
              "api-integrations/agiloft-cc",
+              "api-integrations/agentline",


+2. Go to your dashboard and copy your API key (starts with `sk_live_`)
+
+<Frame>
+  <img src="/api-integrations/agentline/account.png" />


cubic-dev-ai

1 issue found across 4 files

Confidence score: 5/5

In docs/docs.json, the api-integrations/agentline item being out of alphabetical order is a minor docs-maintainability issue; merging as-is is unlikely to affect product behavior but can make future list scans and automated ordering checks noisier — reorder the entry before or in a quick follow-up.

Not reviewed (too large): packages/providers/providers.yaml (~24 lines) - if these are generated or fixture files, add them to ignored paths to exclude them from future reviews.

_{Reply with feedback, questions, or to request a fix.

Re-trigger cubic}

- providers.yaml: fix Bearer *** -> Bearer \ (auth was broken) - providers.yaml: add offset paginate config for list endpoints - providers.yaml: remove invalid prefix field under credentials (schema) - docs.json: place agentline before agiloft (alphabetical) - docs: add api-integrations/agentline.mdx (required by provider validator)

hassan254-prog

Could you run npm run docs to ensure all automatically generated docs is generated correctly?

hassan254-prog · 2026-07-07T11:56:56Z

For this page, I would recommend using the same style as the other docs pages, including the correct sections, structure and Nango form screenshot for consistency.

hassan254-prog · 2026-07-07T11:58:25Z

Similar to this, we should keep the same style and structure to ensure consistency with the rest of our Nango docs.

hassan254-prog · 2026-07-07T12:00:04Z

+        paginate:
+            type: offset
+            offset_name_in_request: offset
+            limit_name_in_request: limit


Suggested change

paginate:

type: offset

offset_name_in_request: offset

limit_name_in_request: limit

We recommend defining this within the functions themselves rather than in the provider configuration.

hassan254-prog · 2026-07-07T12:00:53Z

+            type: string
+            title: API Key
+            description: Your AgentLine API key.
+            pattern: '^sk_live_[a-zA-Z0-9_]+$'


Is it possible for the API key to have a separate format for other environments, such as staging, since this appears to be for live accounts only?

Api is for live accounts only, not possible to have other formats.

- providers.yaml: remove paginate config (define in functions per review) - connect.mdx: align with standard Nango docs structure - agentline.mdx: align with standard Nango docs structure - regenerate auto-generated docs (api-catalog, snippets)

Previous commit introduced CRLF (edit tool under autocrlf=false). Restore LF to match repo convention and keep the PR diff clean.

hassan254-prog

Could you also run npm run docs to update the automatically generated doc files?

hassan254-prog · 2026-07-09T14:43:48Z

+#### Step 2: Enter your API key in Nango
+
+Once you have your **API key**:
+1. In Nango, go to [Connections](https://app.nango.dev/dev/connections) -> _Add Test Connection_ -> select _AgentLine_.
+2. Enter your **API key** in the designated field.
+3. Submit the form, and you should be successfully authenticated.
+
+You are now connected to AgentLine.
+
+<Note>Contribute improvements to the setup guide by [editing this page](https://github.com/nangohq/nango/tree/master/docs/api-integrations/agentline/connect.mdx)</Note>


Please use the same format for this section as compared to the other connect ui docs, and also add the form screenshot, to match the other docs.

hassan254-prog · 2026-07-09T14:44:38Z

+## 📚 AgentLine Integration Guides
+
+- [Connect to AgentLine](/api-integrations/agentline/connect)
+Obtain your AgentLine API key and connect it to Nango.
+
+Official docs: [AgentLine API](https://docs.agentline.cloud)
+
+---


Same with this, this should contain the ## 🧩 Pre-built syncs section.

hassan254-prog · 2026-07-09T14:50:41Z

This should be a valid svg file.

…pre-built syncs) - agentline.mdx: add Pre-built syncs section; fix docs URL (agentline.cloud/docs) - connect.mdx: canonical Step 2 format + add form.png screenshot - llms-full.txt: add agentline row (auto-generated) - add agentline.svg logo + form.png

superagent-security · 2026-07-10T15:17:17Z

+        - communication
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.agentline.cloud


P1: Unverified provider may proxy user API keys to an externally-controlled domain with no independent presence

This PR adds a new "AgentLine" provider whose proxy base_url (https://api.agentline.cloud) receives every configured user's API key as a Bearer token. Independent web searches for the company return no results outside its own recently-launched site, which lists no verifiable company history, team, or physical address, and uses an auto-generated-looking social handle. The PR originates from a freshly created fork (AgentLineHQ/nango) by a contributor with no prior presence in the repo, and the API key pattern ^sk_live_[a-zA-Z0-9_]+$ mirrors Stripe's well-known live-key format. If merged and later adopted, Nango would relay users' credentials to a domain whose operator is not independently established.

Require independent verification of AgentLine's legitimacy (business registration, team identity, industry presence, and a live, documented API at api.agentline.cloud) before merging this provider. Treat the provider config and any logo/branding as untrusted until vetted, and confirm the sk_live_ key format is genuinely AgentLine's and not borrowed from another service.

AI prompt

Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior. <file name="packages/providers/providers.yaml"> <violation number="1" location="packages/providers/providers.yaml:772"> <priority>P1</priority> <title>Unverified provider may proxy user API keys to an externally-controlled domain with no independent presence</title> <evidence>This PR adds a new "AgentLine" provider whose proxy base_url (https://api.agentline.cloud) receives every configured user's API key as a Bearer token (authorization: Bearer ${apiKey}). Independent web searches for the company return no results outside its own recently-launched site, which lists no verifiable company history, team, or physical address and uses an auto-generated-looking social handle. The PR originates from a freshly created fork (AgentLineHQ/nango) by a contributor with no prior presence in the repo, and the API key pattern '^sk_live_[a-zA-Z0-9_]+$' mirrors Stripe's well-known live-key format. If merged and later adopted, Nango would relay users' credentials to a domain whose operator is not independently established.</evidence> <recommendation>Require independent verification of AgentLine's legitimacy (business registration, team identity, industry presence, and a live documented API at api.agentline.cloud) before merging this provider. Treat the provider config and any logo/branding as untrusted until vetted, and confirm the sk_live_ key format is genuinely AgentLine's and not borrowed from another service.</recommendation> </violation> </file>

feat(integrations): add AgentLine provider

517d858

Add AgentLine as a new API_KEY provider: - providers.yaml: agentline entry with communication category - docs: connect.mdx setup guide and account.png logo - docs.json: alphabetical entry in api-integrations

Copilot AI review requested due to automatic review settings July 6, 2026 17:47

Copilot started reviewing on behalf of Sameersribot July 6, 2026 17:47 View session

Copilot AI reviewed Jul 6, 2026

View reviewed changes

cubic-dev-ai Bot reviewed Jul 6, 2026

View reviewed changes

Comment thread docs/docs.json Outdated

hassan254-prog reviewed Jul 7, 2026

View reviewed changes

Sameersribot added 2 commits July 7, 2026 18:13

fix(integrations): restore LF line endings in providers.yaml

01baa8b

Previous commit introduced CRLF (edit tool under autocrlf=false). Restore LF to match repo convention and keep the PR diff clean.

hassan254-prog reviewed Jul 9, 2026

View reviewed changes

Comment thread docs/api-integrations/agentline/account.png

hassan254-prog Jul 9, 2026

Copy link
Copy Markdown

Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a valid svg file.

superagent-security Bot reviewed Jul 10, 2026

View reviewed changes

superagent-security Bot added the pr:flagged PR flagged for review by security analysis. label Jul 10, 2026

		docs: https://nango.dev/docs/api-integrations/agentline
		docs_connect: https://nango.dev/docs/api-integrations/agentline/connect

Uh oh!

Conversation

Sameersribot commented Jul 6, 2026 • edited by cubic-dev-ai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Provider config

Changes

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

hassan254-prog left a comment

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 7, 2026

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 7, 2026

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 7, 2026

Choose a reason for hiding this comment

Uh oh!

Sameersribot Jul 7, 2026

Choose a reason for hiding this comment

Uh oh!

hassan254-prog left a comment

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 9, 2026

Choose a reason for hiding this comment

Uh oh!

hassan254-prog Jul 9, 2026

Choose a reason for hiding this comment

Uh oh!

superagent-security Bot Jul 10, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Sameersribot commented Jul 6, 2026 •

edited by cubic-dev-ai Bot

Loading

cubic-dev-ai Bot left a comment •

edited

Loading

hassan254-prog Jul 7, 2026 •

edited

Loading

hassan254-prog Jul 9, 2026 •

edited

Loading