STEP 1
Connect Cortex and Fynk
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Cortex and Fynk Integration
Build developer tools workflows between Cortex and Fynk on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cortex and Fynk
Detailed info you need to know about Cortex and Fynk integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cortex to Fynk
Set up your Cortex and Fynk integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cortex and Fynk 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 Cortex and Fynk. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cortex and Fynk work in WEXTL?
WEXTL exposes actions and triggers for Cortex and Fynk that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Fynk triggersCortex actions
Fynk modules
- Add a Document Metadata ValueAdds a document metadata value.
- Add a Document PartyAdds a new document party.
- Add a Document SignatoryCreates a new signatory for a document.
- Create a Document from a TemplateCreates a new document from a template.
- Create a Document from an Uploaded PDFCreates a new document from an uploaded PDF file.
- Delete a Document MetadataDeletes a document metadata value.
- Delete a Document SignatoryDeletes a document signatory.
- Download a DocumentDownloads the latest version of a document.
- Get a DocumentRetrieves a single document.
- List Document Metadata ValuesRetrieves a list of document metadata values.
- List Document PartiesRetrieves a list of document parties.
- List Document SignatoriesRetrieves a list of document signatories.
- Make an API CallPerforms an arbitrary authorized API call.
- Move a Document to a Review StageMoves a document to the review stage.
- Move a Document to a Signing StageMoves a document to a signing stage.
- Search DocumentsSearches for documents from an account.
- Update a DocumentUpdates a single document.
- Update a Document Dynamic FieldUpdates a document dynamic field value.
- Update a Document PartyUpdates a document party.
- Update a Document SignatoryUpdates a document signatory.
- Upload a PDF DocumentUploads a PDF document file.
- Watch DocumentsTriggers when documents are created or updated.
Cortex modules
- Delete AnalyzerRemoves a custom analyzer registration.
- Delete JobDeletes a job record.
- Get AnalyzerReturns a single analyzer.
- Get JobReturns a single job.
- Get Job ReportReturns the report for a completed job.
- List AnalyzersRetrieves available analyzers.
- List JobsRetrieves analyzer/responder jobs.
- List RespondersRetrieves available responders.
- Make an API CallPerforms an arbitrary authorized API call.
- Run AnalyzerSubmits an observable to an analyzer.
- Run ResponderRuns a responder against a TheHive entity.
- Submit JobSubmits a file-type observable to an analyzer.
- Update Analyzer ConfigurationUpdates org-level analyzer configuration.
Frequently asked questions
Common questions about connecting Cortex and Fynk.
Connect your Cortex and Fynk accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Fynk's "Watch Documents" fires, WEXTL can "Delete Analyzer" in Cortex. Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer); Fynk has 21 actions (including Add a Document Metadata Value, Add a Document Party, and Add a Document Signatory). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Cortex-to-Fynk automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Cortex (or Fynk) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Cortex + Fynk automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Cortex and Fynk integration.
- Cortex and Fynk integration source code, module specs and credentials implementation.
- Our Cortex and Fynk integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cortex and Fynk — 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.
- Cortex integration information
- Fynk integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library