If I’m going to use Fibery as a staple for my client’s or my own stack, I need to be able to integrate it with other software I use. The easiest way to do that would be a Webhook Trigger which woud allow us to create a Fibery endpoint and trigger the relevant Rule whenever data is received.
Some of my current use cases which would benefit from this:
Creating tasks and sending emails when a third-party webform is received
Logging incoming or outgoing calls and linking them to the correct Contact when a number is dialed
Sending a Slack notification when a Calendly event is booked
Sending a welcome pack and assigning tasks after a contract is signed
I currently have no easy way (i.e. low-code way) to do all that with Fibery.
I know this can be achieved with connectors such as Make and Zapier but these are very pricey and do not scale well when you have high volumes.
Fibery has form view, so it is unlikely that integration with other form software would be prioritised.
What software do you use to log calls?
Fibery integrates with Slack and automations can be made to send notifications when events occur in Fibery.
I’m not sure how/why Fibery could directly help with integrating Calendly with Slack?
Fibery automations would allow you to send information to users when something happens (in Fibery). How are you expecting that Fibery would connect to the signing of a contract? Is there specific SW you use for signing?
Just ran into this while trying integrate mailing into my space. Webhooks are used to update email delivery status, and while it is possible with setting up a n8n space, it is much easier for replication and templating if this feature existed within Fibery. It is something that is in Airtable, and would be a much simpler way to use external tools to influence Fibery, without the need for the full integration API.
That said, I’m not sure about the technical difficulties of making this
@Raphael_Mizrahi1 Webhook trigger is a great suggestion! Fibery is a really good system of record that should be integrated with other software without requiring programming knowledge. The current automations are quite limited in functionality and not the top priority of the Fibery development team (for good reason!).
Therefore I am currently building an advanced automation platform dedicated to Fibery called Fiberflow. I want to address the vast amount of feature requests in this forum regarding advanced automations for Fibery. More automation triggers like “Webhook received”, “Email received” or as simple as “Entity deleted” are on the top of the list as they enable Fibery users to integrate with any other software