Solving Team Collaboration on Nostr: Our Loomly-Zapier Bridge

As our team at Soapbox has grown, we've faced a common challenge in the Nostr ecosystem: how do you enable multiple team members to schedule and publish content without sharing your private key (nsec) with each team member?

This is a fundamental problem that many Nostr teams encounter. Your nsec is your identity on Nostr - sharing it compromises security and makes it impossible to know who actually published what. Yet traditional social media management tools don't support Nostr natively.

Content Scheduling: Loomly + Zapier → Nostr

To solve this problem, we built a bridge that connects Loomly (a content scheduling platform) to Nostr through Zapier. Zapier is automation tool for connecting the APIs of popular applications. While it's not the most "pure-Nostr" approach and it relies on proprietary platforms, it's a practical solution that actually works for real marketing teams with collaboration needs. We are sharing this solution in case it helps your team, too! The bridge works in four steps:

Step 1: Configure Loomly Trigger in Zapier

We set up a Zapier trigger that watches for a "Post Manual Publish" event in Loomly. This means whenever a team member schedules a post on a "custom channel" to go live, it triggers our Zap.

Step 2: Loomly Post Conversion

Following the trigger, the first Zapier code block takes Loomly's post data and converts it into a format suitable for Nostr. This handles:

• Text content formatting
• Image & video attachments
• Hashtag & user tagging parsing

Note: you could probably use this same workflow to any publishing tool that has a Zapier integration! We discuss Loomly here because it's what our team uses, however we encourage the community to explore what other tools work with this system!

You can find the source code for this conversion step here: Loomly Post Conversion on GitLab

Step 3: Nostr Event Signing

The third step handles creating the Nostr event structure and signing it with our nsec.

Step 4: Nostr Event Publishing to Relays

The final step handles publishing the Nostr event to relays via Alby's API

The final two code snippets are not specific to Loomly, and could actually be used to publish Nostr events in response to any trigger. We encourage the community to take this code and expand on it for their own needs!

The uncompiled Nostr event signing and publishing code (steps 3 & 4) is available here: Zapier Nostr Publishing on GitLab

Publishing Nostr Content on Loomly via the Zapier Bridge

Once the Zap is configured, team members can schedule posts in Loomly's custom channel. This works much the same as scheduling any other social post, except for tagging users. This requires adding the user's npub and hex pubkey into the text of the post manually to be parsed and converted into p tags. (See more documentation on formatting Nostr posts in Loomly here.)

Security Considerations 🚨

The biggest downside of this approach is that you do have to provide your nsec to Zapier. This means trusting Zapier to keep it secure, which is a trade-off some teams may be uncomfortable with. Zapier is a reputable platform, but it's still a third party. In the future, someone may expand on what we've started here to allow for another signing pattern that does not requiring putting the nsec into Zapier. However, for now this solution meets the needs of our team.

Building Bridges Helps Grow Nostr

This solution addresses a glaring gap in the Nostr ecosystem. While we wait for native team collaboration tools to mature, practical bridges like this enable businesses and marketing teams to adopt Nostr without abandoning their existing workflows.

We know this is not the most decentralized or "pure" Nostr solution, but it's one that actually works now for real teams. Sometimes the best solution is the one that gets adopted and used, even if it's not perfect.

Explore other Nostr Bridges by Soapbox

This Loomly-Zapier-Nostr bridge continues Soapbox's tradition of building practical bridges between different social protocols and platforms. Our previous work includes:

Our Mostr bridge connects Nostr to Mastodon and the broader Fediverse, allowing users on both protocols to interact seamlessly. This has enabled thousands of cross-protocol conversations and helped grow both communities.

We've also built bridges connecting Nostr to Bluesky's AT Protocol, enabling users to follow Bluesky accounts from Nostr and vice versa. This helps break down the silos between different decentralized social networks.

These bridges serve a crucial role in the decentralized social media ecosystem - they allow users to maintain their preferred protocol while still connecting with friends and communities on other platforms.

Open Source Community

As with all our work at Soapbox, we're sharing this solution openly with the community. The code is available on GitLab, and we encourage other teams facing similar challenges to adapt and improve upon our approach.

If you implement this solution or build upon it, we'd love to hear about your experience. The Nostr ecosystem grows stronger when we share practical solutions to real problems.