nBold Zapier integrationAutomate nBold with Zapier.
The nBold Zapier integration offers 1 trigger, 2 actions and 0 searches, all around Microsoft Teams teams built from nBold templates. Zapier hears when such a team is created, and two actions can read the details and the channels of a team.
Verified Trustpilot reviews · AI, automation & growth agency
What the nBold Zapier integration is good for
nBold automates how Microsoft Teams teams are set up, from templates with their channels, files and tasks. Zapier links it to your other tools through a Zap: an automation made of one trigger (the event that starts it) and one or more actions (what it then does for you). Here the event is a new team built from a template.
An inventory of the teams you create. New Microsoft Teams Team Created Using a Template starts a Zap each time a team comes out of one of your templates, and a sheet or a database can keep the list without anyone typing it.
The full picture of a new team. Get My Microsoft Teams Team by ID reads the details of a team from its Team ID. Whatever step supplies the Team ID, the action hands the team's details to the steps that follow.
Channels passed on to another tool. Get the Channels of a Microsoft Teams Team returns the channels of a team, given its Team ID, so a project tool or a document can mention them.
What Zapier does not do here: the two actions only read, they do not create, change or archive anything in Microsoft Teams, and there is no search. As its name says, the trigger is about teams created using a template. To weigh Zapier against other tools, open our n8n vs Zapier comparison.
Zapier words, in plain English
Seven words are enough for this page. One line each, then they are used as they are.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started. With nBold, both actions read information about a team for the steps that follow.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Reading a team with an nBold action is one task too.
- Instant trigger
- A trigger the app itself reports: it calls Zapier the moment the event happens, so nothing waits for a scheduled check.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it 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.
What an nBold Zap costs
nBold is not a premium app, so it runs on the free plan. Its two actions read data, and each successful read counts as a task.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The trigger never costs a task. Every action that succeeds counts once, including Get the Channels of a Microsoft Teams Team and Get My Microsoft Teams Team by ID; an action that fails is not counted. The free plan gives 100 tasks a month and two-step Zaps, so the trigger plus one action. Reading the team and then writing it somewhere is two actions, a multi-step Zap that needs a paid plan. The interval grid below is Zapier's general one for polling triggers: it does not apply to nBold, whose only trigger is instant.
Connect nBold to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your nBold account linked once, then reused by every step that uses nBold.
- 02
Pick nBold
Type nBold in the search box of the dialog, select it and click Add connection. A new tab opens, and the sign-in of the next step happens there, not in Zapier.
- 03
Sign in and grant access
Sign in to nBold in that tab and give Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first nBold Zap: a register of new teams
GoalEach team created from the template you pick is added as a row in your team register and announced in your team chat.
- 01
Set the trigger
Create a Zap, pick nBold and New Microsoft Teams Team Created Using a Template, then your connection. Choose the template in Template List.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so the mapping is done on a real team.
- 03
Add the row
Add your spreadsheet as the first action and map into its columns the details the trigger test brought back. Test the step and read what came back.
- 04
Add the message
Click the plus icon, add your team chat and write the message from the same details. Two actions make a multi-step Zap, which needs a paid plan.
- 05
Publish
Click Publish to switch the Zap on. Only teams created after that moment start it. For a guided build on your own account, see our Zapier training.
The nBold trigger
1 event starts a Zap when something happens in nBold, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Microsoft Teams Team Created Using a Template
Instant triggerIn Zapier“Triggers when a Microsoft Teams Team is created using a template, including channels, tabs, ...”
When nBold finishes building a Microsoft Teams team from one of your templates, with its channels and tabs, the Zap starts. It is the moment a new team is ready to be announced, recorded or completed elsewhere, and the only event nBold sends to Zapier.
The 2 nBold actions
nBold gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Get the Channels of a Microsoft Teams Team
ActionIn Zapier“Get the Channels of a Microsoft Teams Team.”
Returns the channels of a team. Its Team ID field is required; the field's help asks for the ID of the team whose channels you want.
Get My Microsoft Teams Team by ID
ActionIn Zapier“Get detailed information about a team.”
Reads the detailed information of one team, given its Team ID, which is required, and hands it to the following steps.
When an nBold Zap breaks
Zapier attaches no help article to nBold and no app-specific limit is published. What can go wrong comes from how Zapier works and from the fields the operations require.
These four cases are the ones to check on an nBold Zap. If a Zap still misbehaves after that, see our Zapier troubleshooting guide.
No look back
A Zap only reacts to what happens after you switch it on. Teams created from a template before that are never picked up; listing them is a separate job.The wrong Team ID
Both actions need a Team ID, and no search can look one up. Check at the test what the value you mapped or typed into it brings back.A sudden flood
After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.A Zap that sets itself off
A Zap that writes into the place its own trigger watches can start itself again and again and burn through your tasks. Keep the trigger and the write apart.
Need help automating nBold with Zapier?
A person reads every message.



