Fynk and Rootly Integration
Connect Fynk and Rootly to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Fynk and Rootly
Detailed info you need to know about Fynk and Rootly integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Fynk to Rootly
Set up your Fynk and Rootly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Fynk and Rootly
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Fynk and Rootly nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Fynk and Rootly. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Fynk and Rootly work in WEXTL?
WEXTL exposes actions and triggers for Fynk and Rootly that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Fynk triggersRootly actions
Fynk modules
- Add a Document Metadata Value Fills a metadata field of a document in fynk with a value. Use Value to set text, a boolean, an array or null as the content.
- Add a Document Party Brings another party into a document under a Reference. Describe it with Entity Type, Entity Name and Address, or reuse a saved party through Account Party UUID.
- Add a Document Signatory Registers a signatory on one party of a document by Email. Add a Mobile Phone and Title if you have them.
- Create a Document from a Template Builds a new document from one of your fynk templates. Use Document Name to title it, otherwise the template name is used, and Owner Emails to give ownership to users of your account.
- Create a Document from an Uploaded PDF Turns a PDF added with Upload a PDF Document into a fynk document that starts as a Draft or already Signed. Use Template UUID to copy settings, Team UUIDs to give teams access and Tag UUIDs to tag it.
- Delete a Document Metadata Value Removes one stored metadata value attached to a document in fynk.
- Delete a Document Signatory Deletes a signatory, the person who signs a document.
- Download a Document Downloads the latest revision of a document as a PDF file. The file arrives as PDF File Data.
- Get a Document Reads one document, including its Stage, Document type, Locale and Archived at date.
- List Document Metadata Values Shows the metadata filled in on a document, each entry with its Value, Value source and Computed status. Use Limit to set how many are returned.
- List Document Parties Lists the parties on a document, with their Entity name, Entity type, Scope and whether each Is ready for signing. Use Limit to cap the count.
- List Document Signatories Lists each signatory of a document with Email, Signing order and Party UUID. Set Limit to restrict how many you get.
- Make an API Call Sends a free-form request to the Fynk REST API, signed with your saved credential.
- Move a Document to a Review Stage Advances a document into the review stage and returns the updated document with its new Stage.
- Move a Document to a Signing Stage Puts a document into signing. Use Signature Type to require a simple, advanced or qualified signature, Sequential Signing to ask signers one after another, and Message for the invitation email.
- Search Documents Finds documents. Narrow by Query, Stages, Tags, Teams or Origins, order them with Sort By and Sort Direction, and cap the results with Limit.
- Update a Document Renames a document and sets how it is signed. Use Signature Type and Sequential Signing for the signing process and External Signatory Invitation Message for the email text. Signing settings cannot change once signing has started.
- Update a Document Dynamic Field Writes a new Value into a dynamic field of a document and returns the Name and Type of the field.
- Update a Document Party Updates one party on a document: Reference, Entity Type, Entity Name, Address and Scope.
- Update a Document Signatory Corrects the contact details of a signatory: Email, First Name, Last Name, Mobile Phone or Title.
- Upload a PDF Document Uploads a PDF to fynk and returns its File ID and File URL. Pass the result to Create a Document from an Uploaded PDF.
- Watch Documents Checks fynk on a schedule for documents that were created or updated. Use Trigger on to follow either kind, Stages to narrow it to certain document stages and Limit to cap each check.
Rootly modules
- Acknowledge an Alert Marks an alert as acknowledged. Use Actor Email to record a specific user as the one who did it, when your organization has actor attribution turned on.
- Add a Note to an Alert Writes a Note on the activity feed of an alert, credited to the chosen User.
- Add a Timeline Event to an Incident Writes an Event on the timeline of an incident. Set Visibility to control who can read it.
- Add Subscribers to an Incident Subscribes the chosen Users to updates on an incident. Turn on Skip Users Without Access to a Private Incident to leave out anyone who cannot see it.
- Assign a Role to a User on an Incident Gives a user an Incident Role on a single incident and returns the updated incident.
- Attach Alerts to an Incident Links existing alerts to an incident by their Alert IDs and returns the Incident ID with its Alerts.
- Cancel an Incident Cancels an incident, with an optional Cancellation Message giving the reason.
- Create a Cause Adds a cause that incidents and retrospectives can be traced to. Give it a Name, and a Public Name and Public Description for status pages.
- Create a Functionality Adds a functionality, a capability of your product, from its Name. Link Owner Teams, Owner Users, Environments and Services to show who is behind it.
- Create a Heartbeat Sets up a heartbeat that alerts when pings stop. Define the Interval with its Interval Unit, an Alert Summary, and who to page through Notification Target Type and Notification Target ID.
- Create a Pulse Records a pulse from its Summary. Link Services and Environments, and use Labels, References and Data for extra detail.
- Create a Schedule Creates an on-call schedule from a Name and an Owner. Use Time Zone, Owner Teams and Send Shift Reports to adjust it.
- Create a Service Registers a service from its Name. Link Owner Teams, Owner Users, Related Services and an Alert Urgency to place it in the rest of your setup.
- Create a Severity Adds a severity level from a Name. Use Severity Level to rank how serious it is, and Color and Notify Emails to customise it.
- Create a Status Page Builds a status page titled by Title. Turn Public and Enabled on or off, style it with Header Color and Footer Color, and choose Services and Functionalities to cover.
- Create a Status Page Announcement Posts an announcement to a status page, from its Title and Body. Turn on Notify Subscribers to alert followers.
- Create a Sub-Status Adds a sub-status under a Parent Status, from a Name. Use Position to order it among its siblings.
- Create a Team Forms a responder team called Name. Add Members and Admins, a Color and an Alert Urgency, and switch on Alerts by Email.
- Create an Action Item Adds a follow-up task to an incident from its Summary. Set a Kind, Priority and Due Date, and name an Assignee or Assigned Teams to own it.
- Create an Alert Raises an alert from a Summary. Link Services, Teams and Environments, choose an Alert Urgency, and page someone with Notification Target Type and Notification Target ID.
- Create an Alert Urgency Defines an urgency level from a Name and Description. Use Retrigger After to set how long Rootly waits before alerting again on an unacknowledged alert.
- Create an Environment Adds an environment such as production, from its Name. Use Notify Emails, Color and External ID to describe and link it.
- Create an Escalation Policy Builds an escalation policy from a Name. Use Repeat Count to loop it several times, and Teams and Services to attach it.
- Create an Incident Declares an incident. Add a Title, Severity and Summary, link Services, Environments and Incident Types, and set Private to restrict who can see it.
- Create an Incident Role Defines a role people can hold during incidents, from a Name. Turn on Optional, Enabled or Allow Several Users to shape it.
- Create an Incident Type Adds a type for classifying incidents, from a Name. Use Color and Notify Emails to customise it.
- Create an Override Shift Puts a User on call for a window on a schedule, between Starts At and Ends At in UTC.
- Delete a Cause Deletes a cause used to classify incidents.
- Delete a Functionality Removes a functionality, a product capability, from the catalog.
- Delete a Heartbeat Deletes a heartbeat monitor that expected regular pings.
- Delete a Schedule Removes an on-call schedule from Rootly.
- Delete a Service Deletes the chosen service from the Rootly account.
- Delete a Severity Removes a severity level used for incidents.
- Delete a Status Page Deletes a customer-facing status page from Rootly.
- Delete a Status Page Announcement Removes an announcement posted on a status page.
- Delete a Status Page Event Deletes an incident update that was posted to a status page.
- Delete a Sub-Status Deletes a sub-status that sits under a parent status.
- Delete a Team Removes a team from Rootly once Confirm is turned on, because it cannot be undone.
- Delete an Action Item Deletes an action item from Rootly. Turn on Confirm to go ahead, because it cannot be undone.
- Delete an Alert Urgency Removes an urgency level that alerts can carry.
- Delete an Environment Removes an environment from your Rootly catalog.
- Delete an Escalation Policy Deletes a paging policy from Rootly.
- Delete an Incident Removes an incident and its record from Rootly.
- Delete an Incident Role Removes a role that responders can take during incidents.
- Delete an Incident Timeline Event Deletes one chronology entry from the timeline of an incident.
- Delete an Incident Type Removes a type used to classify incidents.
- Delete an Override Shift Deletes a temporary on-call override from a schedule.
- Detach an Incident from Its Parent Separates a child incident from the parent incident it was grouped under.
- Escalate an Alert Raises an alert to a higher level of an escalation policy. Name the Escalation Policy and Escalation Policy Level, or leave the level empty for the next one.
- Get a Cause Looks up a cause with its Slug, Public Name and Position.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Fynk and Rootly integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Fynk and Rootly.
References
List of sources used to gather information about the Fynk and Rootly integration.
- Fynk and Rootly integration source code, module specs and credentials implementation.
- Our Fynk and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Fynk and Rootly, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Fynk integration information
- Rootly integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Fynk and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.

