Resources · Zapier integration

Loomly Zapier integrationAutomate Loomly with Zapier.

The Loomly Zapier integration gives you 12 triggers, 2 actions and 0 searches. Every trigger is instant: Loomly tells Zapier about a new post, a comment or a failed publish as it happens. The two actions add a Quick Post or a Custom Post Idea to a calendar.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Loomly Zapier integration actually does

The integration connects Loomly, a platform where marketing teams plan, review and publish their social media posts together, to the other apps you use. A Zap (an automation built in Zapier) can start from something that happens in a Loomly calendar, or create a post or an idea in one.

Three results come up again and again. A publishing alarm: Post Publish Failed starts a Zap the moment a post does not go out to a channel, so someone hears about it before the audience notices the gap. A review loop that leaves Loomly: New Comment Left on Post and Post State Updated push collaborator feedback and status changes to wherever your team actually reads. A calendar filled from outside: Create Quick Post and Create Custom Post Idea turn a row, a form entry or a request into a dated item in a Loomly calendar.

One detail changes the maths on a free plan: all 12 Loomly triggers are instant. Loomly reports each event to Zapier itself, so the 15-minute wait of the free plan never applies to them.

What Zapier does not do here: there is no search, so a Zap cannot look up an existing Loomly post to edit it. There is no action to update, publish or delete a post either. Zapier creates items in a calendar and listens to what happens there, and that is all. To weigh this against other platforms, the n8n vs Zapier and Make vs Zapier comparisons are the place to look.

Vocabulary

Zapier vocabulary in one minute

Seven words come back all over this page. Here they are in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new post in a Loomly calendar. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or creates something for you, like a Quick Post in Loomly.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is reported by the app as soon as the event happens. Loomly only has instant ones.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What a Loomly Zap really costs

Zapier bills tasks, and a task is an action that worked. The Loomly trigger itself never costs anything.

  • Loomly premium appNo, works on the free plan
  • Loomly triggers12, all instant
  • Free plan100 tasks a month, two-step Zaps
  • Failed actionNot billed

Each successful action is counted on its own, so a Zap with three actions uses three times the tasks of a one-action Zap. A failed action is not counted. Loomly is not a premium app, so the free plan accepts it: 100 tasks a month, unlimited Zaps, but two steps per Zap, one trigger and one action. A Loomly trigger followed by one action fits; add a filter or a second action and you need a paid plan. The grid below is how often Zapier checks a polling trigger on each plan. It does not apply to Loomly's triggers, which are all instant, only to a polling trigger from another app that feeds a Loomly action.

Connect

Connect Loomly to Zapier in three steps

  1. 01

    Open your Apps page

    In your Zapier account, open the Apps page and click + Add connection. A connection is your Loomly account linked to Zapier once, then reused by every Loomly step in every Zap.

  2. 02

    Pick Loomly

    Search for Loomly in the dialog, select it, then click Add connection. Use the Loomly account that can see the calendars you want to automate, since every step will ask you to choose one.

  3. 03

    Sign in and grant access

    A new tab opens on Loomly. Sign in, then grant Zapier access to the account. Back in the editor, the connection appears in the account list of each Loomly trigger and action.

First Zap

Your first Loomly Zap

GoalWhen a Loomly post fails to publish to a channel, send a message to your team chat, but only for the failures that pass your filter, so the right person republishes it by hand.

  1. 01

    Create the Zap

    Create a new Zap and choose Loomly as the app that starts it. In the event list, pick Post Publish Failed, then select your Loomly connection.

  2. 02

    Choose the calendar

    Set the required Calendar field to the calendar you want to watch. One Zap watches one calendar, so a second calendar means a second Zap.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent items from that calendar, so you map fields on a real post rather than on empty placeholders.

  4. 04

    Add a filter

    Click the plus icon and add a Filter step. Set its three boxes: a field the trigger brought back, the rule, and the value to compare with. The filter makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Add the chat action

    Click the plus icon, pick your team chat app and its send-message action. Map the post fields Loomly returned into the message text and the channel.

  6. 06

    Test and publish

    Test the action once and read what came back. Then click Publish. Only failures that happen from now on reach the chat.

Triggers

The 12 Loomly triggers

12 events start a Zap when something happens in Loomly, and 12 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Custom Post Idea Created

Instant trigger

In Zapier“Triggers when a new Custom Post Idea is created in a Calendar.”

Starts a Zap whenever someone adds a Custom Post Idea to a Loomly calendar, so an idea jotted down in Loomly can travel to the place where your team tracks its content backlog.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your content team keeps a shared list of ideas elsewhere and wants every Loomly idea copied there.
Watch out
the Zap watches the single calendar you pick; ideas added to other calendars are ignored.
2

New Invite Sent to Collaborator

Instant trigger

In Zapier“Triggers when an invite is sent to a Collaborator to join a Calendar.”

Fires each time a collaborator is invited to join a calendar, which gives you a clean starting point for onboarding steps outside Loomly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone new gets invited to a calendar, and you want a welcome note or a line in your access log without typing it yourself.
Watch out
it reacts to the invite being sent, not to the person accepting it.
3

Item Added to Library

Instant trigger

In Zapier“Triggers when a new item (photo, video, note) is added to a Calendar's Library.”

Reacts when a photo, a video or a note lands in a calendar's Library, the shared asset space of Loomly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new visuals keep landing in the Library and the people writing posts should hear about each one without opening Loomly to check.
Watch out
the Library belongs to a calendar, so pick the right Calendar or the Zap stays silent.
4

New Post Created

Instant trigger

In Zapier“Triggers when a new Post is created.”

This is the broad one: any new post created in Loomly starts the Zap, whoever wrote it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep a running record of planned posts in a spreadsheet or a project tool, and each draft should appear there as soon as it exists.
Watch out
a Zap that writes posts into the very calendar it watches sets itself off again and again.
5

New Comment Left on Post

Instant trigger

In Zapier“Triggers when a new (Loomly) Comment is left on a Loomly Post by a Collaborator.”

When a collaborator leaves a Loomly comment on a post, the Zap starts and carries that comment with it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
reviewers comment in Loomly but writers live in their team chat, and feedback keeps getting missed.
Watch out
these are comments left inside Loomly by collaborators, not comments from your audience on the social networks.
6

New Quick Post Created

Instant trigger

In Zapier“Triggers when a Quick Post is created in a Calendar.”

Narrower than New Post Created: only Quick Posts added to the chosen calendar start the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team uses Quick Posts for fast, reactive content and you want a separate alert for those, apart from planned posts.
Watch out
the Create Quick Post action makes exactly this kind of post, so never point both at the same calendar in one Zap.
7

Post Assignment Updated

Instant trigger

In Zapier“Triggers when a Post Assignment is updated.”

Changing who a post is assigned to is enough to start this Zap, which makes handovers visible outside Loomly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a post moves from the writer to the approver, and the new owner should get a direct ping in the tool they check first.
Watch out
every reassignment fires, including going back to the previous person, so a filter on the assignee keeps noise down on a paid plan.
8

Post State Updated

Instant trigger

In Zapier“Triggers when a Post State is updated.”

Follows the life of a post: each time its state changes in Loomly, the Zap runs with the new state attached.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a status board outside Loomly should mirror where each post stands in your approval flow.
Watch out
it fires on every change of state, so if only one state matters to you, add a filter on that field, which makes the Zap multi-step.
9

Post Edited

Instant trigger

In Zapier“Triggers when the content of a Post (date, channels, copy, media) is edited within Loomly.”

Catches edits to the content of a post: its date, its channels, its copy or its media.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a post was already approved and someone changes the copy or moves the date afterwards, and the approver needs to know.
Watch out
each edit is a new event, so a post reworked several times starts several runs, and each run bills the actions behind it.
10

Post Publish Failed

Instant trigger

In Zapier“Triggers when a Loomly Post has failed publishing to a Channel.”

Runs when Loomly could not publish a post to one of its channels, the event nobody wants to discover late.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you schedule posts ahead and need an alert the moment one does not go out, so it can be republished by hand.
Watch out
the Zap tells you it failed; fixing the channel and republishing still happens in Loomly.
11

Post Publish Required

Instant trigger

In Zapier“Triggers when a Loomly Post is due to be published and requires manual publishing.”

Some posts cannot go out automatically. When one of them reaches its date and needs someone to publish it manually, this trigger starts the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the person in charge of a channel should get a reminder in their own tool when it is time to post.
Watch out
the Zap only reminds; the manual publishing itself is still a human step.
12

Post Publish Successful

Instant trigger

In Zapier“Triggers when a Loomly Post is published to a Channel.”

Confirms a post went live: once Loomly publishes it to a channel, the Zap starts with the post details.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you log every published post in a spreadsheet for reporting, or let the person who asked for it know it is live.
Watch out
it watches the one calendar picked in the Calendar field, so a second calendar needs its own Zap.
Actions

The 2 Loomly actions

Loomly gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Custom Post Idea

Action

In Zapier“Creates a Custom Post Idea in a Calendar.”

Puts an idea, not a post, on a Loomly calendar: a title and a start date that the team can turn into content later.

When to use it
ideas are collected outside Loomly and should land in the calendar where planning happens.
Watch out
Calendar, Start On and Title are all required.
2

Create Quick Post

Action

In Zapier“Creates a Quick Post in a Calendar.”

Adds a Quick Post to a Loomly calendar from data another app supplies, with its date and subject already filled in.

When to use it
requests for posts arrive through a form or a spreadsheet and you want them dropped straight into the calendar.
Watch out
Calendar, Date and Subject are required; the network fields are optional, one per channel.
When it breaks

When a Loomly Zap breaks

Zapier attaches no help article to Loomly and documents no limit specific to the app. What goes wrong comes from Zapier's general rules.

Three cases explain most Loomly Zaps that stall or misbehave. If none matches what you see, the Zapier troubleshooting page is the next stop.

  • Old posts never go through

    A Zap only reacts to what happens after you publish it. Posts already in the calendar are not picked up; moving that history is a separate job.
  • Create Quick Post sets off its own trigger

    A Zap that creates a Quick Post in the calendar its New Quick Post Created trigger watches starts itself again and burns through tasks.
  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.
Need help

Need help automating Loomly with Zapier?

A person reads every message.

FAQ

Loomly Zapier integration: frequent questions

01Is the Loomly Zapier integration free?
Yes, within the limits of the free plan. Loomly is not a premium app, so a free Zapier account can use it. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. A Loomly trigger followed by a single action, or another app's trigger followed by Create Quick Post, fits. A filter or a second action makes the Zap multi-step, and that needs a paid plan or the free trial.
02How many tasks does a Loomly Zap use?
One task for each action that completes successfully. The Loomly trigger itself never costs anything, and neither does Zapier listening for events. A Zap with one action uses one task per run, a Zap with three actions uses three. An action that fails is not counted. Keep in mind that Post Edited fires on each edit, so a post reworked several times starts several runs, and each run bills its actions again.
03Is the Loomly Zapier integration real time?
Yes for every Loomly trigger. All 12 are instant: Loomly calls Zapier the moment the event happens, and the Zap starts right away whatever your plan. The polling grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) only matters if your Zap starts from another app's polling trigger and then uses a Loomly action. A Zap built on an instant trigger shows a lightning bolt in the editor.
04What does it take to connect Loomly to Zapier?
A Loomly account, plus access to the calendars you want the Zap to touch. Open the Apps page of your Zapier account, click + Add connection, search for Loomly, click Add connection, sign in in the tab that opens and grant Zapier access. If a calendar belongs to someone else, your account needs read or write access on it, otherwise it will not appear in the Calendar field that every Loomly step requires.
05Why is a calendar missing from the Loomly step?
Because the connected Loomly account cannot reach it. Every Loomly trigger and both actions ask for a Calendar, and the list only shows calendars that the connected account can see. If a colleague owns the calendar, ask them for access in Loomly, or connect the account that already has it. Also remember that one step watches or writes to one calendar: covering two calendars means two Zaps, or a second action on a paid plan.
06What if the Loomly operation you need does not exist in Zapier?
Zapier only offers what is listed here: 12 triggers and 2 actions, both of which create items. There is no search, and no action to edit, publish or delete a post. If the step you have in mind is not among these, Zapier cannot do it with Loomly today. Check whether Loomly can handle it on its own side, or whether another automation platform connects to Loomly with the operation you are after.
07Zapier, Make or n8n for Loomly?
Compare them on criteria, not on reputation, because each one fits a different setup. On Zapier, Loomly offers 12 instant triggers and 2 creation actions and a two-step Zap runs on the free plan. On another platform, check first whether Loomly is available, which events and operations it exposes, and how runs are counted. The deciding points are usually your volume of posts, who maintains the automations, and which apps sit around Loomly in your process.