We have added Fibery modules to Integromat — a no-code automation and integration platform:
This is purely thanks to your requests since we hadn’t had the integration in our initial plans.
Here is a blog post with some examples and comparisons to Zapier: https://fibery.io/blog/integromat.
Also, a long and boring step-by-step tutorial: Due Date Reminder | Integromat Tutorial - YouTube.
What scenarios are you looking to implement with the new Fibery modules?
What modules are missing?
Wow! As a heavy integromat user I’m really happy you did this!
This is great - thanks @antoniokov Already using to extract data from Fibery and put into Google Docs (dirt simple content management) and trying to get Phantombuster > Fibery going.
One thing - I needed to fall back on Make an API call to get a rich text field out. It would be great if that was automated.
HI @antoniokov. I’m trying to create an Integromat flow where I create an entity “Contact” and relate it to “Organisation”. If the Organisation does not exist I create the Organisation, then create the Contact and relate the Organisation I have just created.
This case repeatedly fails validation in Integromat “BundleValidationError”, presumably because the ID doesn’t exist in the collection BEFORE the flow starts. Please advise if this is a limitation and any possible fix.
It’s great that we now have Integromat and Zapier to choose from, but does this mean that delivering native automation has dropped down the priority list? I hope not.
There are many things that I’d like to be automatic, but I’d prefer to keep it all in one place, especially the simpler things.
For example, I presume it would be possible using Integromat/Zapier automation to be able to create the effect of ‘dependent’ relationships (i.e. where a linked child item cannot exist once the parent item stops existing) but this ought to be native I feel.
Similarly, I know that there are requests on these boards that relate to updating one or more of an entity’s fields when the workflow state changes. Possible with Integromat/Zapier, but nice to be native.
One other thing, I’ve noticed that the Integromat ‘Watch Events’ includes the ability to trigger when an entity is deleted, but one of the issues is that the output of the module seems to be only the Type ID and Entity ID (presumably because the other fields of the now-deleted item can’t be retrieved).
Is there a chance it could be improved so as to provide the full entity info (pre-deletion fields etc.) as the module output?
One thing - I needed to fall back on Make an API call to get a rich text field out. It would be great if that was automated.
Absolutely! We’ve added the rich-text Fields:
I’m trying to create an Integromat flow where I create an entity “Contact” and relate it to “Organisation”. If the Organisation does not exist I create the Organisation, then create the Contact and relate the Organisation I have just created.
I’d suggest starting the flow from the Organization’s side:
Luckily, no (;
Native automation is too important: for example, we cannot include Zaps as part of our App templates. Automation is such a fundamental part of the platform, that we are not willing to exclusively rely on the 3rd parties.
For example, I presume it would be possible using Integromat/Zapier automation to be able to create the effect of ‘dependent’ relationships (i.e. where a linked child item cannot exist once the parent item stops existing) but this ought to be native I feel.
Totally makes sense. Most likely, this will be possible with native automation.
One other thing, I’ve noticed that the Integromat ‘Watch Events’ includes the ability to trigger when an entity is deleted, but one of the issues is that the output of the module seems to be only the Type ID and Entity ID (presumably because the other fields of the now-deleted item can’t be retrieved).
Is there a chance it could be improved so as to provide the full entity info (pre-deletion fields etc.) as the module output?
We’ll take a look and I’ll come back with an update.
Not easy for us to implement, unfortunately. We’ll collect the feedback and put in the effort if this pops up often.
Meanwhile, for entities that shouldn’t exist without parents, you could rely on the “relation has changed” trigger for the child entities — if the relation Field has become empty, delete the entity.
Maybe I’m being stupid, but I can’t see how I can use integromat to delete an entity (unless I should use the ‘Make an API call’, and I don’t fancy that).
Am I missing something?
So far, only via an API call indeed.
It’s our Integromat connector, not you, that is missing something (;
We’ll take a look if it’s easy to add the Delete an Entity action.
We’ll add the Delete an Entity action with the next Integromat module’s update. Integromat has to review and approve it first, so can’t give an ETA. But it’s coming!
It’s a pity “File” field is missing 
I’m trying to auto-create Candidates in Hiring app from Gmail, wanted CV attached to email to be attached to Candidate. Is there is any way except through API?
I’m afraid, the API is the only way so far.
Created an item in our backlog though – we’ll pay a closer look at similar scenarios.
