feat(integrations): add AgentLine provider #6700
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| --- | ||
| title: 'AgentLine' | ||
| sidebarTitle: 'AgentLine' | ||
| description: 'Integrate your application with the AgentLine API' | ||
| --- | ||
|
|
||
| AgentLine is the voice infrastructure for AI agents — phone numbers, calls, and SMS through a single API. | ||
|
|
||
| ## 🚀 Quickstart | ||
|
|
||
| Connect to AgentLine with Nango and see data flow in 2 minutes. | ||
|
|
||
| <Steps> | ||
| <Step title="Create the integration"> | ||
| In Nango ([free signup](https://app.nango.dev)), go to [Integrations](https://app.nango.dev/dev/integrations) -> _Configure New Integration_ -> _AgentLine_. | ||
| </Step> | ||
| <Step title="Connect AgentLine"> | ||
| Go to [Connections](https://app.nango.dev/dev/connections) -> _Add Test Connection_ -> _AgentLine_ -> enter your API key and click _Authorize_. See the [connect guide](/api-integrations/agentline/connect) for how to obtain a key. | ||
| </Step> | ||
| <Step title="Call the AgentLine API"> | ||
| Let's make your first request to the AgentLine API. Replace the placeholders below with your [secret key](https://app.nango.dev/dev/environment-settings), [integration ID](https://app.nango.dev/dev/integrations), and [connection ID](https://app.nango.dev/dev/connections): | ||
| <Tabs> | ||
| <Tab title="cURL"> | ||
|
|
||
| ```bash | ||
| curl "https://api.nango.dev/proxy/v1/agents" \ | ||
| -H "Authorization: Bearer <NANGO-SECRET-KEY>" \ | ||
| -H "Provider-Config-Key: <INTEGRATION-ID>" \ | ||
| -H "Connection-Id: <CONNECTION-ID>" | ||
| ``` | ||
|
|
||
| </Tab> | ||
|
|
||
| <Tab title="Node"> | ||
|
|
||
| Install Nango's backend SDK with `npm i @nangohq/node`. Then run: | ||
|
|
||
| ```typescript | ||
| import { Nango } from '@nangohq/node'; | ||
|
|
||
| const nango = new Nango({ secretKey: '<NANGO-SECRET-KEY>' }); | ||
|
|
||
| const res = await nango.get({ | ||
| endpoint: '/v1/agents', | ||
| providerConfigKey: '<INTEGRATION-ID>', | ||
| connectionId: '<CONNECTION-ID>' | ||
| }); | ||
|
|
||
| console.log(res.data); | ||
| ``` | ||
|
|
||
| </Tab> | ||
| </Tabs> | ||
| Or fetch credentials with the [Node SDK](/reference/sdks/node#get-a-connection-with-credentials) or [API](/reference/api/connection/get). | ||
|
|
||
| ✅ You're connected! Check the [Logs](https://app.nango.dev/dev/logs) tab in Nango to inspect requests. | ||
| </Step> | ||
|
|
||
| <Step title="Implement Nango in your app"> | ||
| Follow our [Auth implementation guide](/guides/primitives/auth) to integrate Nango in your app. | ||
| </Step> | ||
| </Steps> | ||
|
|
||
| ## 📚 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) | ||
|
|
||
| --- | ||
|
Comment on lines
+64
to
+79
Contributor
There was a problem hiding this comment. Same with this, this should contain the |
||
|
Contributor
There was a problem hiding this comment. This should be a valid svg file. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
|
Contributor
There was a problem hiding this comment. 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| --- | ||
| title: AgentLine - How do I link my account? | ||
| sidebarTitle: AgentLine | ||
| --- | ||
|
|
||
|
|
||
| # Overview | ||
|
|
||
| To authenticate with AgentLine, you need an **API key** — a Bearer token that grants access to your AgentLine account (phone numbers, calls, and SMS). | ||
|
|
||
| This guide will walk you through finding your API key within AgentLine and connecting it to Nango. | ||
|
|
||
| ### Prerequisites: | ||
|
|
||
| - You must have an **AgentLine account**. Sign up at [agentline.cloud](https://agentline.cloud). | ||
|
|
||
| #### Step 1: Finding your API key | ||
|
|
||
| 1. Sign up or log in at [agentline.cloud](https://agentline.cloud). | ||
| 2. Go to your dashboard and copy your API key (starts with `sk_live_`). | ||
|
|
||
| <img src="/api-integrations/agentline/account.png" /> | ||
|
Contributor
There was a problem hiding this comment. The image here is still incorrect. |
||
|
|
||
| <Tip>Keep your API key secret — it grants full access to your AgentLine account.</Tip> | ||
|
|
||
| #### 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> | ||
|
Contributor
There was a problem hiding this comment. 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. |
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| ## Pre-built tooling | ||
| <AccordionGroup> | ||
| <Accordion title="✅ Authorization"> | ||
| | Tools | Status | | ||
| | - | - | | ||
| | Pre-built authorization (API Key) | ✅ | | ||
| | Pre-built authorization UI | ✅ | | ||
| | Custom authorization UI | ✅ | | ||
| | End-user authorization guide | ✅ | | ||
| | Expired credentials detection | ✅ | | ||
| </Accordion> | ||
| <Accordion title="✅ Read & write data"> | ||
| | Tools | Status | | ||
| | - | - | | ||
| | Pre-built integrations | 🚫 (time to contribute: <48h) | | ||
| | API unification | ✅ | | ||
| | 2-way sync | ✅ | | ||
| | Webhooks from Nango on data modifications | ✅ | | ||
| | Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) | | ||
| | Proxy requests | ✅ | | ||
| </Accordion> | ||
| <Accordion title="✅ Observability & data quality"> | ||
| | Tools | Status | | ||
| | - | - | | ||
| | HTTP request logging | ✅ | | ||
| | End-to-end type safety | ✅ | | ||
| | Data runtime validation | ✅ | | ||
| | OpenTelemetry export | ✅ | | ||
| | Slack alerts on errors | ✅ | | ||
| | Integration status API | ✅ | | ||
| </Accordion> | ||
| <Accordion title="✅ Customization"> | ||
| | Tools | Status | | ||
| | - | - | | ||
| | Create or customize use-cases | ✅ | | ||
| | Pre-configured pagination | 🚫 (time to contribute: <48h) | | ||
| | Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) | | ||
| | Per-customer configurations | ✅ | | ||
| </Accordion> | ||
| </AccordionGroup> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| _No pre-built syncs or actions available yet._ | ||
|
|
||
| <Tip>Not seeing the integration you need? [Build your own](/guides/functions/functions-guide) independently.</Tip> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -763,6 +763,29 @@ affinity-v2: | |
| example: 'nrlW2KR5m-qUCA-rTqKb_EUK1swERlenqn70KNMMrTM' | ||
| doc_section: '#step-1-generating-your-api-key' | ||
|
|
||
| agentline: | ||
| display_name: AgentLine | ||
| categories: | ||
| - communication | ||
| auth_mode: API_KEY | ||
| proxy: | ||
| base_url: https://api.agentline.cloud | ||
|
There was a problem hiding this comment. 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 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 AI prompt |
||
| headers: | ||
| authorization: Bearer ${apiKey} | ||
| verification: | ||
| method: GET | ||
| endpoints: | ||
| - /v1/agents | ||
| docs: https://nango.dev/docs/api-integrations/agentline | ||
| docs_connect: https://nango.dev/docs/api-integrations/agentline/connect | ||
|
Comment on lines
+779
to
+780
|
||
| credentials: | ||
| apiKey: | ||
| type: string | ||
| title: API Key | ||
| description: Your AgentLine API key. | ||
| pattern: '^sk_live_[a-zA-Z0-9_]+$' | ||
|
Contributor
There was a problem hiding this comment. 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?
Author
There was a problem hiding this comment. Api is for live accounts only, not possible to have other formats. |
||
| doc_section: '#step-1-finding-your-api-key' | ||
|
|
||
| agiloft: | ||
| display_name: Agiloft | ||
| categories: | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to this, we should keep the same style and structure to ensure consistency with the rest of our Nango docs.