Integromat is a powerful no-code automation and integration platform, "the glue of the internet" is how they describe it.
Connect Fibery to the rest of your tools and let the machine take over repetitive tasks:
Get notified in Microsoft Teams when someone assigns you to a task in Fibery.
Sync new leads from HubSpot CRM to Fibery.
Create a new branch in Bitbucket when a user story progresses into a specific state in Fibery.
Alternatively, try Zapier — it's more expensive but easier to learn.
If your goal is to sync data into Fibery, see if we have a native Integration and possibly save a few hours of your precious life.
⚡️ An entity is created, updated, or deleted.
(instant, unlike in our Zapier connection)
(search by text, date, and checkbox Fields)
Create an entity.
Update an entity.
Due date reminder
Every morning send each teammate a list of tasks that are due today via Slack:
Level 1 — Notify me
Let's pretend you are a manager and all communications must go through you 😈
Prepare sample data in Fibery: create a couple of tasks, set the due dates to today, and assign different people.
Add a new Integromat scenario and schedule it to run once a day.
Start with Fibery's Find entities module: look for the tasks that are due today.
Add Slack's Create a message module: pick your IM and compose the message.
"[Name]" is due today
Level 2 — Clickable links
Navigating to Fibery tasks from Slack would be nice:
Add Compose a string module and build a Slack-formatted link for each task.
Use this text instead of the task name in the Slack module.
[Text] is due today
Level 3 — Fibery users 🤝 Slack users
In order to send a reminder to each teammate, we link Fibery users to Slack users:
Slack IDtext Field to Fibery's User and paste the IDs of a couple of test users.
Add another Fibery's FInd entities module to look for a User, hardcode your User's public ID for now.
Replace your IM with
Slack IDthat comes from Fibery in the Slack module.
Level 4 — Notify assignees
Stop pretending you're an evil manager — let's send reminders to the actual assignees:
Add the Iterator module to split each task with multiple assignees into several bundles (see the diagram below).
Use real Users' IDs when looking for a User in Fibery.
Feel free to stop at this point.
Level 5 — One person, one message (optional)
Wouldn't it be nice to get the list of tasks in a single message?
Add the Array aggregator module to combine several tasks for each person into a single bundle, group by assignee's ID.
Use the ID from the Array aggregator when looking for a User in Fibery.
Convert the array of tasks back into text to send the Slack message.
join(map([array]; "value"); [newline])
You should definitely stop here:
Level 6 — Error handling (really optional)
Wouldn't it be great to retry on failures?
Enable storing of Incomplete Executions in the scenario settings.
Add the Break module to all Fibery and Slack modules.
Check Automatically complete execution in all Break modules.
Add Sleep modules to later Fibery and Slack modules to halt the execution of parallel bundles if an error occurs.
Level 7 — Prevent duplicate notifications (really optional)
How do we prevent duplicate reminders on retries? Each time we send a reminder, we'll remember the person and the date:
Create a Data Store with
Fibery User ID(text) and
Add a record to the Data Store after sending a message to Slack.
[Key]-[Today]— record key for easy search.
Check if a record exists before looking for a User in Fibery.
[Key]-[Today]— told ya.
Set up a filter: proceed to search only if the record doesn't exist.