Resources · Zapier integration

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

Overview

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.

Vocabulary

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.
Cost

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

Connect nBold to Zapier in three steps

  1. 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.

  2. 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.

  3. 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.

First Zap

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Triggers

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.

1

New Microsoft Teams Team Created Using a Template

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a register of every team created from your project template, without anyone filling it in.
Watch out
the Template List field is required, so a template has to be picked there before the trigger can be tested.
Actions

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.

1

Get the Channels of a Microsoft Teams Team

Action

In 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.

When to use it
a project tool or a shared document should list the channels of a team whose Team ID you already have.
Watch out
look at the test result to see how the channels come back before mapping them.
2

Get My Microsoft Teams Team by ID

Action

In 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 to use it
you hold the Team ID of a team, typed in or carried by an earlier step, and the next step needs that team's details.
Watch out
it is an action, so each successful read is a task, and with a second action the Zap is multi-step.
When it breaks

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

Need help automating nBold with Zapier?

A person reads every message.

FAQ

nBold and Zapier: the questions people ask

01Is the nBold Zapier integration free?
Yes. nBold is not a premium app, so it runs on the free plan, which gives 100 tasks a month and an unlimited number of Zaps of two steps each: one trigger, one action. The new team trigger followed by a row in a sheet fits. The Zap on this page does not, because it writes a row and then posts a message; a second action or a filter makes a multi-step Zap, which needs a paid plan.
02How many tasks does an nBold Zap use?
One per successful action, and nothing for the trigger. The catch with nBold is that its two actions only read data, yet each read is still an action, so it counts. The Zap on this page, a row then a message, uses two tasks per new team when both steps go through, and adding Get My Microsoft Teams Team by ID would make three. An action that fails is not counted. Zapier also notes that a few apps and a few actions take more than one task when they complete.
03Does an nBold Zap start right away?
Yes. Its only trigger, New Microsoft Teams Team Created Using a Template, is instant: nBold tells Zapier the moment it happens, so the Zap starts right away, whatever your plan. The plan's polling interval, 15 minutes on the free plan, does not apply to it. In the editor, a Zap built on an instant trigger shows a lightning bolt. The steps after the trigger then run one after the other.
04What does it take to connect nBold to Zapier?
An account on nBold, plus read or write access on anything you do not own yourself and want the Zap to touch. Then open Apps in Zapier, click + Add connection, pick nBold, sign in in the tab that opens and grant access. Before building, note that the trigger's Template List field is required, and that both actions ask for a Team ID. The connection is made once, then reused by every nBold step of every Zap.
05Does the trigger fire for every new team in Microsoft Teams?
No. New Microsoft Teams Team Created Using a Template only starts for teams that nBold builds from a template, as its name and its official description say. Its Template List field is required, so a template has to be chosen there. If several templates matter to you, check in the editor what Template List lets you pick, and run the test to see which teams come back before you publish the Zap.
06What if the nBold operation you need is not listed?
Look at the nBold page on Zapier, which shows the current list. Today it holds one trigger and two actions that read a team and its channels; nothing creates or changes a team from a Zap. If you need data rather than a change, the two read actions may already be enough. If you need to act on Microsoft Teams, compare how another automation tool handles that need before building around the gap.
07Zapier, Make or n8n for nBold?
Choose on criteria, not on a ranking. On Zapier, ask first whether one instant trigger and two read actions cover the job. Then count the cost: each read is a task, and reading plus writing elsewhere means a paid plan. Timing is not an issue here, since the trigger is instant and no polling interval applies. Put the same questions to Make and n8n, operations available and cost per run, before you decide.