STEP 1
Select Swish in workflow
Pick Swish app in the workflow builder [4] - just one click to select the app.
Swish Integration
Mobile payment service for instant bank-to-bank transfers (Sweden). Keep Swish financial workflows accurate without repetitive manual updates. Start from Retrieve Consent and send the resulting data through Retrieve Payment Request or Retrieve Payout.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Swish integration
Triggers can detect changes in Swish and run actions that can create, search or modify data inside Swish automatically [3] — exactly how you set them.
- Retrieve ConsentRetrieve the details and current status of a consent.
- Retrieve Payment RequestRetrieve the details and current status of a Swish payment request.
- Retrieve PayoutRetrieve the details and current status of a Swish payout.
- Retrieve RefundRetrieve the details and current status of a Swish refund.
- Cancel Payment RequestCancel a Swish payment request that has not yet been completed.
- Check Recurring Availability (Alias)Check if a user is eligible for recurring payments using their phone number.
- Check Recurring Availability (TIN)Check if a user is eligible for recurring payments using their tax identification number.
- Create ConsentCreate a consent request to allow recurring payments from a customer.
- Create Consent TokenCreate a consent token for recurring payments that can be used to open the Swish app.
- Create Payment RequestCreate a Swish payment request for a customer. The customer will receive the request in the Swish app and can approve the payment there.
- Create PayoutCreate a payout to send money to a Swish user.
- Create RefundCreate a refund for a completed Swish payment.
- Delete Scheduled PaymentDelete a scheduled recurring payment before it is processed.
- Generate Prefilled QR CodeGenerate a QR code with pre-filled payment details that the customer can review and confirm.
- Generate QR CodeGenerate a QR code for a Swish payment request that customers can scan to pay.
- Make An API CallPerforms an arbitrarily authorized API request.
- Update Consent Callback URLUpdate the callback URL for an existing consent.
How to integrate Swish in automation workflow?
3 simple steps to make your Swish connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect Swish
When prompted, authorize access to Swish in WEXTL once. Swish credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Swish account. Approve?
STEP 3
Build a workflow
Build your workflow with Swish yourself or with WEXTL® AI Builder. Connect Swish to any available integrations [5], or use HTTP node to go beyond them.
Swish
How Swish connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Swish app is called in workflows. That allows your finance automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Swish supports.
The following table illustrates what fields Swish integration require during authorization flow inside our workflow builder [4].
Connect Swish
Environment*Text
••••••••
Swich - Client Certificate*Text
••••••••
Demonstration of Swish connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
EnvironmentRequired | select | Select the environment to connect to. MSS is recommended for development and testing. |
Swich - Client CertificateRequired | cert | Upload your client certificate (.pem or .p12) for secure authentication. |
Connect Swish to popular apps on WEXTL
Enter a name of the other app you want to sync with Swish below. Click on selected app to explore integration options with Swish. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with Swish integration
Select Retrieve Consent action from Swish - this will be a starting point in your automation. Whenever event happens in Swish, workflow will start [7] from Retrieve Consent node.
Search for Create Consent Token, connect it as the next step of integration sequence. You can use filters between Retrieve Consent and Create Consent Token, so only important data pass from Retrieve Consent to the next step. WEXTL gives you full control over the process of Swish automation. All parts of workflow are visible on the canvas [4].
Swish on WEXTL has 17 modules for building finance automations. Explore Swish documentation for more.
Video slide demonstrates how Retrieve Consent and Create Consent Token [6] nodes are used in Swish workflow.
Frequently asked questions
Common questions about automating Swish in your workflows.
Swish has no triggers, but it provides 17 actions including "Retrieve Consent", "Retrieve Payment Request", and "Retrieve Payout". Pair them with triggers from other apps to automate Swish tasks.
Integration has 17 actions, including "Retrieve Consent", "Retrieve Payment Request", and "Retrieve Payout", and more. Refer to our Swish Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The Swish integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Swish official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where Swish provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Swish or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Swish inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Swish modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the Swish integration.
- Swish integration source code, module specs and credentials implementation.
- Internal Swish integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Swish vendor API documentation — 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.
- WEXTL® Apps Library
- WEXTL® Swish App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation