Plek Zapier integrationAutomate Plek with Zapier.
The Plek Zapier integration gives you 1 trigger, 5 actions and 0 searches. A slash command typed in a Plek chat can start a Zap instantly, and Zaps can publish posts and infopages, message a group, and add or remove users on your intranet.
Verified Trustpilot reviews · AI, automation & growth agency
What the Plek Zapier integration can do for your intranet
Plek is a social intranet: news posts, information pages, group chat and a staff directory in one place. Through Zapier, other tools can publish into it, manage its user list and talk to its groups, while a slash command typed in Plek chat can kick off work elsewhere, the instant it is typed.
Three outcomes worth building. Announcements that publish themselves: Create Post drops a new post in a group whenever something happens in another tool, a release, a new policy, a calendar event. A staff list that follows HR: Create New User and Remove One User or Multiple Users add arrivals and remove leavers from Plek based on what your HR tool says. Commands that do real work: Chat Message That Can Make Trigger turns a /command typed by a colleague into a Zap, which can log a request, open a ticket or reply to the group with Send Chat Message to Group.
What Zapier does not do here. There is only one trigger, so a new post, a new user or a new infopage in Plek cannot start a Zap. There is no search step either: a Zap cannot look up an existing Plek user by email, so removing someone needs their user ID from an earlier step. And creating users is reserved to admin accounts.
Before you go further, the Zapier review is worth a read.
Zapier words, in plain English
First time on Zapier? These eight terms cover the whole page.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. For Plek, it is a colleague typing a /command in one of its chats.
- Action
- What the Zap does once started: the step that writes, sends or removes something for you, here in Plek.
- Task
- The unit Zapier bills. One task equals one action your Zap completes successfully; your plan counts those.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for a scheduled check. Plek's is one.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. Plek has none of these.
- Filter
- A step that lets the Zap continue only when the incoming item meets your condition, and stops it otherwise.
- Connection
- Your Plek account linked to Zapier once, then reused by every step that uses Plek. Its rights are the Zap's rights.
What it really costs
Plek is not a premium app: it works on the free plan. The slash-command trigger never costs a task, and because it is instant, the polling grid of the plans does not slow it down.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on free2 steps: one trigger, one action
- Trigger cost0 tasks
- Trigger typeInstant, plan interval does not apply
Tasks are counted per successful action. A Zap that creates one post per announcement costs one task each time. A Zap that creates a user and then messages a group costs two. Failed actions are not counted. The free plan only builds two-step Zaps, one trigger and one action. Adding a filter, a second action or a search turns it into a multi-step Zap, which needs a paid plan. Count your actions before you build, not after.
Connect your Plek account
- 01
Add the connection
In Zapier, open the Apps page of your account and click + Add connection. In the dialog that appears, type Plek in the search box and pick it from the list.
- 02
Sign in to Plek
Click Add connection. A new tab opens on Plek. Sign in with the account whose rights the Zap should use, ideally a dedicated admin account rather than your own.
- 03
Grant access
Allow Zapier to reach the Plek account. The connection is then reused by every Plek step in every Zap, so you set it up once and pick it from a list afterwards.
Your first Zap: a /command that publishes a post
GoalA colleague types a /command in Plek chat, and a post appears in the right group.
- 01
Pick the trigger
Create a Zap, choose Plek as the app and Chat Message That Can Make Trigger as the event. Select your Plek connection and continue.
- 02
Test it on a real command
Type a /command in a Plek chat, then run the test. Zapier brings back the three most recent items, so you can map fields from a real message.
- 03
Add a filter (paid plans)
Add a filter so only one command goes on: pick the field, the rule and the value. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add Create Post
Add the Create Post action, choose the group, then map the title and the content from what the trigger returned. Both are required.
- 05
Test, then publish
Test the action and check the post in Plek. Click Publish to switch the Zap on. Commands typed before that moment are not picked up.
The Plek trigger
1 event starts a Zap when something happens in Plek, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Chat Message That Can Make Trigger
Instant triggerIn Zapier“Triggers when user types a /command.”
Starts a Zap when someone types a /command in a Plek chat. It turns your intranet chat into a control panel: a colleague types a short command, and the work happens in another tool without anyone opening it.
The 5 Plek actions
Plek gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Infopage
ActionIn Zapier“Creates a new infopage”
Publishes a new information page in Plek, with a title and a body. Good for reference content that should live on the intranet rather than in a feed.
Create New User
ActionIn Zapier“Creates a new user, only admins are allowed to create new users. Make sure you have admin-rights!”
Adds a person to Plek with a first name, last name, email and role. Two optional boxes decide whether a magic login link goes out and whether the welcome email is skipped.
Remove One User or Multiple Users
ActionIn Zapier“Remove one user or multiple users”
Takes one or several people out of Plek in a single step. You give it the user IDs of the people to remove, not their names.
Create Post
ActionIn Zapier“Create a new post.”
Adds a new post to a Plek group, the news-feed side of the intranet. You pick the group, then fill in a title and a body.
Send Chat Message to Group
ActionIn Zapier“Send a chat message to a selected group.”
Drops a chat message into the group you choose. Shorter and more immediate than a post, it lands in the conversation rather than in the feed.
When it breaks
Zapier links no help article to Plek and no app-specific limit is documented. The cases below are general Zapier limits that hit Plek Zaps in practice.
Plek Zaps fail less on errors than on setup choices: rights, history and loops. Check these four first, and if the answer is not there, the Zapier troubleshooting page.
Earlier commands are ignored
A Zap only reacts to what happens after you switch it on. Commands typed, users added or posts made before that are never picked up.The Zap keeps setting itself off
A Zap that writes into the very chat its trigger watches can start itself again and again, burning through tasks. Keep the command out of the reply.A bulk burst gets held back
If a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of running them.User creation is refused
Create New User is reserved to admins. A Zap connected with a regular account fails on that step; reconnect with an account that has admin rights.
Need help automating Plek with Zapier?
A person reads every message.
