Loops.so, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Loops.so account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Connects with a key
- 12 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Loops.so is
The email platform for modern SaaS. A better way to send product, marketing, and transactional email.
You paste in a key from your own Loops.so account. It is kept encrypted, and you can withdraw it from inside Loops.so whenever you like.
One message in, the work done in Loops.so.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Loops.so. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Loops.so account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Loops.so
These are the ready-made tools your AI employee already has in Loops.so. It is not limited to them, but it never has to be taught these.
- Create ContactTool to add a new contact to your Loops audience. Use when you need to create a contact with email and optional properties like name, subscription status, or custom attributes. Ret
- Create Contact PropertyTool to add a custom contact property to your Loops team. Use when you need to store additional contact data beyond default fields. Properties must have unique names in camelCase f
- Delete ContactTool to delete a contact by email address or user ID. Use when you need to remove a contact from Loops. Either email or userId must be provided to identify the contact.
- Find ContactTool to search for a contact by email or userId. Use when you need to find a specific contact's details including subscription status and custom properties. Exactly one of email or
- Get Contact PropertiesTool to retrieve a list of your account's contact properties from Loops.so. Use when you need to view all available contact properties or filter to only custom properties created b
- Get Dedicated Sending IPsTool to retrieve a list of Loops' dedicated sending IP addresses. Use when you need to get IP addresses for whitelisting purposes.
- Get Mailing ListsTool to retrieve all mailing lists associated with your Loops account. Use when you need to browse or manage mailing list information.
- List Custom FieldsTool to retrieve a list of custom contact properties. Use when you need to view available custom fields for contacts. Note: This endpoint is deprecated in favor of 'List contact pr
- List Transactional EmailsTool to retrieve a list of published transactional emails. Use when you need to view all available transactional email templates. Supports pagination with perPage and cursor parame
- Send EventTool to send events to trigger emails in Loops. Use when you need to track user actions and trigger automated email workflows based on those events.
- Test API KeyTool to test API key validity and retrieve team information. Use to verify API credentials are working correctly.
- Update ContactTool to update an existing contact by email or userId. Use when you need to modify contact properties or re-subscribe contacts. Creates a new contact if no matching record exists.
You stay the boss of your Loops.so account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Loops.so account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Loops.so is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Loops.so and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Loops.so
- Can an AI employee really work inside Loops.so?
- Yes. It signs in to your own Loops.so account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Loops.so?
- No. Nothing moves and nothing is replaced. Your records stay in Loops.so, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Loops.so account?
- You paste in a key from your own Loops.so account. It is kept encrypted, and you can withdraw it from inside Loops.so whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Loops.so?
- It has 12 ready-made tools in Loops.so today, among them Create Contact, Create Contact Property and Delete Contact. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Loops.so and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Loops.so and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Loops.so?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Loops.so is written down with what it did and when.