Skip to content

Add Fortnox connector as Independent Publisher #3843

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

mathiastornblom
Copy link

This pull request adds a new Independent Publisher connector for Fortnox, a Swedish cloud-based platform used by businesses and accounting firms to manage financial operations.


Publisher

Mathias Törnblom

API Used

Fortnox REST API v1
🔗 https://developer.fortnox.se/

Authentication

OAuth 2.0 (Authorization Code Grant)

Connector Scope

The connector allows access to core Fortnox features such as:

  • Account management
  • Customer records
  • Invoicing
  • Order creation

Validation

The connector has been tested and validated using Power Platform CLI and Power Automate.


Screenshots

✅ Get Account

Get Account

✅ List Customers

List Customers

✅ Create Invoice

Create Invoice

✅ Custom Connector Test Tab

Get Customer

✅ OAuth Config

(Optional but included for reviewer clarity)
oAuth


Submission Checklist

  • The connector does not already exist on Power Platform
  • All operations have been tested successfully
  • All operations and parameters are documented in the swagger
  • Response schemas are defined where applicable
  • Swagger validated using Power Platform CLI and/or Swagger Editor
  • No invalid brand color used (Independent Publisher does not include icon)
  • PR is named Fortnox (Independent Publisher)
  • 3 successful Flow runs attached
  • Test tab screenshot attached
  • OAuth setup instructions are in the readme.md

Please let me know if any changes are needed.

@mathiastornblom mathiastornblom requested a review from a team as a code owner April 13, 2025 22:37
@vmanoharas
Copy link
Contributor

Hi @mathiastornblom,

Please fix all the swagger validation errors.

##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/1accounts1{Number}/get/responses/200/schema/properties/Account/properties/Active/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/~1currencies/get/responses/200/schema/properties/Currencies/items/properties/IsAutomatic/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/1currencies1{Code}/get/responses/200/schema/properties/Currency/properties/IsAutomatic/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/1vouchers1{VoucherSeries}~1{VoucherNumber}/get/responses/200/schema/properties/Voucher/properties/VoucherRows/items/properties/Removed/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/~1absencetransactions/get/responses/200/schema/properties/AbsenceTransactions/items/properties/HolidayEntitling/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/~1absencetransactions/post/parameters/2/schema/properties/AbsenceTransaction/properties/HolidayEntitling/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/~1absencetransactions/post/responses/201/schema/properties/AbsenceTransaction/properties/HolidayEntitling/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/1absencetransactions1{id}/get/responses/200/schema/properties/AbsenceTransaction/properties/HolidayEntitling/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/1absencetransactions1{id}/put/parameters/3/schema/properties/AbsenceTransaction/properties/HolidayEntitling/enum
##[error]The type of the enum value is 'String' but it should be 'Boolean' as specified in the schema. ValuePath: /paths/1absencetransactions1{id}/put/responses/200/schema/properties/AbsenceTransaction/properties/HolidayEntitling/enum
##[error]The value 'title' contains at least one of the restricted words: 'api, connector'. ValuePath: /info/title
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1customers/get/parameters/0
##[error]The 'description' property is required. ValuePath: /paths/~1customers/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1customers/get/parameters/1
##[error]The 'description' property is required. ValuePath: /paths/~1customers/get/parameters/1
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1customers/get/parameters/2
##[error]The 'description' property is required. ValuePath: /paths/~1customers/get/parameters/2
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1customers/get/parameters/3
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1customers1{CustomerNumber}/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1customers1{CustomerNumber}/delete/parameters/0
##[error]The 'description' property is required. ValuePath: /paths/1customers1{CustomerNumber}/delete/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/0
##[error]The 'description' property is required. ValuePath: /paths/1invoices1/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/1
##[error]The 'description' property is required. ValuePath: /paths/1invoices1/get/parameters/1
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/2
##[error]The 'description' property is required. ValuePath: /paths/1invoices1/get/parameters/2
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/3
##[error]The 'description' property is required. ValuePath: /paths/1invoices1/get/parameters/3
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/4
##[error]The 'description' property is required. ValuePath: /paths/1invoices1/get/parameters/4
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/5
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1/get/parameters/6
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1{DocumentNumber}~1preview/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1invoices1{DocumentNumber}/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1currencies1{Code}/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1vouchers/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1vouchers/get/parameters/3
##[error]The 'description' property is required. ValuePath: /paths/~1vouchers/get/parameters/3
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1vouchers/get/parameters/4
##[error]The 'description' property is required. ValuePath: /paths/~1vouchers/get/parameters/4
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1vouchers/get/parameters/5
##[error]The 'description' property is required. ValuePath: /paths/~1vouchers/get/parameters/5
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1vouchers/get/parameters/6
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1vouchers1{VoucherSeries}~1{VoucherNumber}/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1vouchers1{VoucherSeries}~1{VoucherNumber}/get/parameters/1
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1vouchers1{VoucherSeries}~1{VoucherNumber}/get/parameters/2
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/0
##[error]The 'description' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/1
##[error]The 'description' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/1
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/2
##[error]The 'description' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/2
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/~1absencetransactions/get/parameters/3
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1absencetransactions/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1absencetransactions/post/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/1absencetransactions1{id}/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/1absencetransactions1{id}/put/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/1absencetransactions1{id}/delete/responses/default

@mathiastornblom
Copy link
Author

Updated the apiDefinition_original.swagger.json in my branch. Now with no validation errors from the PowerPlatform CLI tool. Please re validate

@mathiastornblom
Copy link
Author

Updated the apiDefinition_original.swagger.json in my branch. Now with no validation errors from the PowerPlatform CLI tool. Please revalidate @vmanoharas

Copy link
Contributor

@vmanoharas vmanoharas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dear Partner

I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants