Loops Connector for Muse
Manage email contacts, trigger automations, send transactional email.
- What
- Manage email contacts, trigger automations, send transactional email.
- Cost
- Free
- Needs
- A Loops API key (Loops Settings > API), kept in your Muse's secure vault (never paste secrets here). Note: keys are per account; creating/updating contacts, firing events, and sending emails are writes — confirm the recipient and payload first. Loops has a free tier.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that manages Loops email contacts and trigger sends: look up a contact by email, keep contacts current with create/upsert, fire custom events for automations, and send transactional emails from a template. Sending a real email is a write — the skill confirms the recipient and payload first, and double-checks the template id. Reading needs no confirmation. Honest note: Loops keys are per account — a key from one Loops account cannot touch another. Loops has a free tier. Draft: written from Loops's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A Loops API key (Loops Settings > API), kept in your Muse's secure vault (never paste secrets here). Note: keys are per account; creating/updating contacts, firing events, and sending emails are writes — confirm the recipient and payload first. Loops has a free tier. No GitHub account needed unless listed here. Install "Loops Connector for Muse" for me. A Muse agent skill that manages Loops email contacts and trigger sends: find and upsert contacts, fire automation events, send transactional emails. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/loops 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "loops". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Loops API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.