360Score.me Zapier integrationAutomate 360Score.me with Zapier.
The 360Score.me Zapier integration listens for one thing: a new shoutout. 1 trigger, 0 actions, 0 searches. When a colleague praises someone in 360Score.me, Zapier can pass it on to another tool. Here is the cost, the setup and the traps.
Verified Trustpilot reviews · AI, automation & growth agency
What the 360Score.me Zapier integration is for
It takes the shoutouts people send each other inside 360Score.me and lets another app act on them. Recognition that would stay buried in one tool can show up where the team actually spends its day, without anyone forwarding it by hand or pasting it into a chat.
Three results people get from the single New Shoutout trigger. A public thank-you in the team chat, so a kind word reaches everyone and not only the person named. A running log of shoutouts in a spreadsheet, which HR can scan at review time instead of digging through the app. A short email to the manager of the person praised, so good work does not go unnoticed one level up.
The best news on this page: New Shoutout is an instant trigger. 360Score.me tells Zapier the moment a shoutout is sent, so the plan's checking interval never applies. Even on the free plan, the message lands right away.
Now the limits. Zapier offers no action and no search for 360Score.me. A Zap cannot create a shoutout, launch a survey or look anything up in the app. Survey results, 360 reviews and anonymous feedback stay inside 360Score.me too. The integration only reports one event outward. If you need to push data into 360Score.me, Zapier is not the route, and the n8n vs Zapier comparison is a good place to weigh other options.
Zapier vocabulary, in one minute
Seven words keep coming back below. Here they are in plain language.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Here, a new shoutout in 360Score.me.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, always in another app here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts those and nothing else.
- Polling vs instant
- A polling trigger is checked on a timer at a fixed interval. An instant trigger is reported by the app itself, the moment it happens.
- Filter
- A step that lets the Zap go on only when the incoming data meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app so later steps can use it. 360Score.me offers none.
What shoutouts cost you in Zapier tasks
The shoutout itself is free to catch. You pay for what the Zap does next, in another app.
- Trigger costFree, never billed
- Free plan100 tasks a month, two-step Zaps only
- New ShoutoutInstant, no interval on any plan
The trigger never costs a task. Each action that completes after it does, and an action that fails is not counted. Post every shoutout to a chat channel and each one uses one task. The free plan gives 100 tasks a month and unlimited Zaps, capped at two steps: one trigger and one action. 360Score.me is not a premium app, so it runs on the free plan. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below only matters for polling triggers, not this one.
Connect 360Score.me in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A connection is your 360Score.me account linked once and reused by every Zap that listens to it. You need an existing account on 360Score.me.
- 02
Find 360Score.me
Type 360Score.me in the search box of the dialog, select it, then click Add connection. A new tab then opens on the 360Score.me side, where you sign in.
- 03
Sign in and allow access
Log in to 360Score.me in that tab and grant Zapier access. The connection then shows up in your list, ready for any Zap. If the account belongs to someone else in your company, ask them for access before you start.
Your first Zap: post every shoutout, then log it
GoalA new shoutout in 360Score.me is posted in a chat channel, then added to a spreadsheet log.
- 01
Start with New Shoutout
Create a Zap, pick 360Score.me as the starting app and New Shoutout as the event. Choose the connection you just added a moment ago.
- 02
Test the trigger
Run the test. Zapier pulls the three most recent shoutouts, so you can pick one and see exactly what data the next steps can use.
- 03
Add the chat action
Click the plus icon, add your chat app and its message action, then map the shoutout fields into the text. Write it once, and every future shoutout fills it in.
- 04
Add the log
Add a second action that writes a row in a spreadsheet. Two actions make this a multi-step Zap, so it needs a paid plan, and each shoutout now uses two tasks.
- 05
Test, then publish
Test the action and read what came back, then publish the Zap to switch it on. Shoutouts sent before that moment will not be posted.
The 360Score.me trigger
1 event starts a Zap when something happens in 360Score.me, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Shoutout
Instant triggerIn Zapier“Triggers when a new shoutout is received from co-worker in an organization in 360Score.me.”
Starts your Zap each time someone in your organization receives a shoutout from a co-worker in 360Score.me. Every step after it can reuse the details of that shoutout, so the praise travels to another tool without anyone copying it over.
When the Zap breaks
Zapier links no help article to 360Score.me, so the known failure points are the general ones.
With a single instant trigger, most problems look the same: a shoutout that never reaches its destination, or one that reaches it too often. Start with these four cases, and turn to the Zapier troubleshooting guide when they do not explain it.
Past shoutouts never show up
A Zap only reacts to what happens after you switch it on. Shoutouts sent before publishing are not picked up, and moving that history is a separate job.The Zap keeps setting itself off
If a later step writes back into the very place the trigger watches, the Zap fires again and again, and each loop burns another task.A big batch gets held back
When a trigger suddenly returns a huge batch at once, after an import or a migration, Zapier's flood protection can hold it back instead of running every item.Nothing to map at test time
The trigger test only brings back the three most recent shoutouts. With none sent on the connected account yet, there is no real record to build the next steps on.
Need help automating 360Score.me with Zapier?
A person reads every message.
