Connecting an AI assistant to your account
An AI assistant can do two things for you with Laposta. It can read this manual and answer your questions about it, and it can use the API to actually work in your account: looking up and updating subscribers, preparing a campaign, and calculating results.
Connecting your account to an assistant
To let an assistant work in your account, you need an API key. Anyone with that key can read your entire subscriber database and send emails on your behalf. An assistant with such a key can therefore do everything you can. Treat it like a password.
Create a separate key for your assistant, so you can revoke it without breaking your other integrations. There is no sandbox environment: every call directly affects the real account associated with the key. Therefore, start with a test list containing a handful of your own email addresses, not your actual database.
Connecting with the Laposta skill
There is a ready-made skill that already knows the entire API: all endpoints, required fields, error codes, and pitfalls. You do not need to explain anything; just type what you want. In Claude Code, you can install the skill with two lines. It also works on claude.ai and in other assistants that follow the Agent Skills standard.
The skill automatically asks for confirmation before deleting, scheduling, or sending anything. It also always sends a testmail first and reads your key from the environment rather than from the conversation.
Connecting with ChatGPT without a skill
In ChatGPT, you can create a custom GPT with an Action and provide the OpenAPI schema of the Laposta API. You can find that schema in the API reference. ChatGPT does have requirements: descriptions may be at most 300 characters per endpoint. OpenAI indicates that this limit may change, so it is best to shorten the schema to the endpoints you actually use.
With a custom GPT, the key is linked to the GPT and not to the user. Anyone allowed to use such a GPT will therefore be working in your account. Never share a GPT containing your Laposta key publicly.
What you can ask the assistant to do
The API consists of seven parts. All details can be found in the API reference.
You can also combine these parts. “Check the results of the last three campaigns to see who never opened them, and put those people on a separate list” is a single sentence for you and a series of calls for the assistant.
What an assistant cannot do
An assistant cannot do more than the API can. The main limitations:
- An assistant can assign labels, but cannot create them itself. In the API, Labels are stored as a field on the subscriber, and only labels that already exist on the list are accepted. You can create a new label on the list yourself via Subscribers → your list → ‘Labels’.
- Campaigns created in the editor cannot be populated via the assistant. An assistant can place the HTML of a campaign created via the API or via an import, but not that of a campaign you built in the drag & drop editor.
- Creating segments does not work reliably. Reading and reusing them works well, but compiling a new segment definition does not. Create the segment in the app and let the assistant use it afterwards.
- There is a limit of 30 requests per minute on a free account and 120 on a paid account. With large numbers of subscribers, this will take a while. See: API limits and error messages.
Using AI in an automation platform
If you prefer working with a fixed flow rather than a conversation, you can also connect Laposta to an automation platform and insert an AI step in between. For example, a subscription comes in, a model determines the industry from the email address, and Laposta places the result in a field.
Working safely with an assistant
An assistant carries out what it thinks you mean. That goes well almost all the time, and sometimes it does not, and when sending campaigns you only notice the difference afterwards.
Never let an assistant send campaigns independently. Once a campaign has been sent, you cannot recall it, and a second attempt will send it again. Agree that the assistant must first send a testmail, then tell you how many people it involves, and only send it after you confirm.
In addition, agree on the following with your assistant:
- Deleting only happens with your approval. This also applies to emptying a list and removing a field, as doing so deletes the data of all your subscribers in that field.
- Unsubscribing is not the same as deleting. “Take Sarah off the newsletter” usually means unsubscribing. Specify which of the two you mean.
- Do not ask for the entire database. Subscriber data is personal data. Have the assistant retrieve only what is needed for your question and nothing more.
- Revoke the key when you are done or if it has ended up somewhere it does not belong. You can do this yourself in your account.