When new type in Fibery, sync it to Raindrop.io.
When a new type is created in Fibery, sync bookmark or tag details to Raindrop.io.
See all Raindrop.io + Fibery integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Raindrop.io Explore Raindrop.io →
TriggersFires when a new page or article is saved in Raindrop.io.
Fires when a saved item in Raindrop.io is tagged or archived.
Saves a page or link to Raindrop.io.
Tags a saved item's record in Raindrop.io.
Fibery Explore Fibery →
TriggersFires when a new task, job or item is created in Fibery.
Fires when a task in Fibery is marked complete.
Fires when a task's due date in Fibery is coming up.
Fires when a task, job or project changes status in Fibery.
Creates a new task, job or item in Fibery.
Updates a task's status or assignee in Fibery.
Posts a comment on a task in Fibery.
Assigns a task in Fibery to a team member.
Common questions
Can Knit build “When new type in Fibery, sync it to Raindrop.io.” between Raindrop.io and Fibery?
Yes — describe it in the box above and Knit's Integrations Agent researches Raindrop.io and Fibery's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.