STEP 1
Connect Cockpit and TinyFish
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Cockpit and TinyFish Integration
Connect Cockpit and TinyFish 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 trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cockpit and TinyFish
Detailed info you need to know about Cockpit and TinyFish integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cockpit to TinyFish
Set up your Cockpit and TinyFish integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cockpit and TinyFish 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 Cockpit and TinyFish. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cockpit and TinyFish work in WEXTL?
WEXTL exposes actions and triggers for Cockpit and TinyFish 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.
TinyFish triggersCockpit actions
TinyFish modules
- Cancel RunCancel a running automation that was started asynchronously.
- Create a Browser SessionCreate a remote browser session and retrieve a CDP connection URL.
- Create a Vault ConnectionConnect a password manager and sync available credential items.
- Delete a Browser SessionTerminate an active browser session.
- Delete Vault ProviderDisconnect a vault provider and remove cached credential items.
- Fetch ContentFetch and extract clean content from one or more URLs.
- Get a RunRetrieve the current or final state of an automation run.
- List Fetch UsageSearch and filter fetch operation history.
- List RunsSearch and filter automation runs.
- List Vault ConnectionSearch and filter vault provider connections linked to the account.
- List Vault ItemsRetrieve available credential items for automation runs.
- Make an API CallExecutes a custom authenticated request to any TinyFish API endpoint.
- Run AutomationRun an AI-powered browser automation workflow on a website and wait for the final result.
- Run Automation AsyncStart an AI-powered browser automation workflow and return the run ID immediately.
- Search WebSearch the web and retrieve structured search results.
- Sync Vault ItemsSync the latest credential items from connected vault providers.
- Watch Fetch UsageTriggers when new fetch usage records are created.
- Watch RunsTriggers when automation runs are created or their status changes.
Cockpit modules
- Create CollectionCreates a new content model.
- Create EntryCreates a new content entry.
- Delete EntryDeletes a content entry.
- Get CollectionReturns a single content model by name.
- Get EntryReturns a single content entry.
- List CollectionsRetrieves content models (collections).
- List EntriesRetrieves entries for a content model.
- Make an API CallPerforms an arbitrary authorized API call.
- Save EntryCreates or updates a content entry.
- Update CollectionUpdates an existing content model.
- Update EntryUpdates an existing content entry.
Frequently asked questions
Common questions about connecting Cockpit and TinyFish.
Connect your Cockpit and TinyFish 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 TinyFish's "Watch Fetch Usage" fires, WEXTL can "Create Collection" in Cockpit. Cockpit has 11 actions (including Create Collection, Create Entry, and Delete Entry); TinyFish has 16 actions (including Cancel Run, Create a Browser Session, and Create a Vault Connection). 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. Cockpit-to-TinyFish 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 Cockpit (or TinyFish) 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 Cockpit + TinyFish 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 Cockpit and TinyFish integration.
- Cockpit and TinyFish integration source code, module specs and credentials implementation.
- Our Cockpit and TinyFish integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cockpit and TinyFish — 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.
- Cockpit integration information
- TinyFish integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library