Connect your app to Attention
You can connect your Lovable app to Attention, a sales conversation platform, to read meeting details and scorecards, or write back updates and QA results. This lets you build tools like dashboards or coaching apps using your sales conversations.
Anyone building an app that needs to interact with sales call data from Attention, especially if their sales team already uses it.
Do this, in order
- 1
Log in to your Attention account.
You need to access your Attention settings to create an API key.
- 2
Go to your profile avatar in the top-left corner and select 'Settings'.
This opens the settings menu where you can find API key management.
- 3
In the sidebar, under 'Organization', choose 'API Keys'.
This is where you manage the keys that allow other applications to connect to Attention.
- 4
Click '+ Create API Key', give it a name like 'Lovable integration', and create it.
This generates a unique key for your Lovable app to use for secure access.
- 5
Copy the API key that appears and save it somewhere safe, as you won't see it again.
This key is like a password; you'll need it for the next step, and it's crucial to keep it secure.
- 6
In Lovable, go to 'Connectors' and select 'Attention'.
This is where you manage all your connections to external services.
- 7
Click 'Add connection'.
You're starting the process to link your Lovable workspace to your Attention account.
- 8
Give your connection a display name (e.g., 'Attention Prod'), paste your copied API key, and decide if you want to share this connection with others in your workspace.
The display name helps you identify the connection, the API key authenticates Lovable with Attention, and sharing controls who else can use it.
- 9
Click 'Connect'.
Lovable will check if the key is valid and then establish the connection, allowing your apps to use Attention data.
Paste this into your project
Connect my Lovable app to Attention. I need to read meeting transcripts and scorecards, write back snippets and QA results, and ask natural-language questions across my sales conversations. I have an Attention API key ready.
Words decoded
- API key
- A secret code that acts like a password, allowing one computer program (like your Lovable app) to securely access another program's services (like Attention).
- Bearer token
- A specific type of API key that grants access to a resource simply by possessing it, like a ticket to an event.
- Semantic AI endpoint
- A part of Attention's system that understands the meaning of your natural language questions, rather than just matching keywords, to find relevant information in your sales calls.
- Rate limits
- Restrictions on how many requests your app can make to Attention's system within a certain time period, to prevent overuse.
- Retry-with-backoff
- A strategy where your app waits for progressively longer periods before trying again if a request fails, to avoid overwhelming the system and increase the chance of success.
- Edge functions
- Small pieces of code that run closer to your users, often used to handle tasks like retrying failed requests or processing data before it reaches your main app.
Where people get stuck
- Do not share your API key publicly, as it functions like a password and gives access to your Attention data.
- Be aware that the Attention API key inherits the permissions of the admin who created it, meaning any Lovable app linked to that connection can read and write any data the key has access to in Attention.
- Only link the Attention connection to Lovable projects that should have full read and write access to your Attention data.
- Remember that all API requests made through this connector count towards your Attention plan limits and are billed directly by Attention, not Lovable.
- If your Attention API key is revoked or rotated, you will need to generate a new one and reconnect it in Lovable, as there is no automatic refresh.
- Understand that the Attention connector cannot receive real-time events; you'll need to poll the API on a schedule if you need updated information.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.