STEP 1
Connect Cockpit and swiDOC
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 swiDOC Integration
Align data between Cockpit and swiDOC to automate developer tools workflows. Actions made in Cockpit integration can trigger sequences of multiple actions inside swiDOC app - automatically, without any line of code.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cockpit and swiDOC
Detailed info you need to know about Cockpit and swiDOC integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cockpit to swiDOC
Set up your Cockpit and swiDOC integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cockpit and swiDOC 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 swiDOC. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cockpit and swiDOC work in WEXTL?
WEXTL exposes actions and triggers for Cockpit and swiDOC 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.
Cockpit actionsswiDOC actions
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.
swiDOC modules
- Get DocumentReturns a document's file content and metadata.
- Get Document MetadataReturns metadata for a stored document.
- Make an API CallPerforms an arbitrary authorized API call.
- Update Document MetadataUpdates selected metadata on a stored document.
- Upload DocumentUploads a file into the swiDOC archive.
Frequently asked questions
Common questions about connecting Cockpit and swiDOC.
Connect your Cockpit and swiDOC accounts once, pick an action in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: use Cockpit's "Create Collection" action to perform swiDOC's "Get Document" action. Cockpit has 11 actions (including Create Collection, Create Entry, and Delete Entry); swiDOC has 5 actions (including Get Document, Get Document Metadata, and Make an API Call). Add filters and transforms between steps when you need them. [1]
Yes — pick an action in either app, then an action in the other, and map the fields between them. [2]
No. Cockpit-to-swiDOC 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 swiDOC) 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 + swiDOC 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 swiDOC integration.
- Cockpit and swiDOC integration source code, module specs and credentials implementation.
- Our Cockpit and swiDOC integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cockpit and swiDOC — 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
- swiDOC integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library