RunMags apps and publishing integrations

Choose connected services around your publishing workflow

The RunMags app store brings together apps and integration options that support a magazine publishing business. Start with the handover you want to improve: collecting an advertiser payment, moving billing information into accounting, signing an agreement or connecting a website. This makes it easier to evaluate a service's purpose and the setup your team will need.

Payments, accounting and signatures

Stripe is an integration option for payment collection. Describe which advertiser or subscription payments you want to collect, which business entity receives them and how finance will reconcile the result. Confirm the supported setup rather than assuming that connecting an account completes the entire process.

The accounting options are QuickBooks Online sync, Xero accounting sync and Fortnox accounting sync. The important discussion includes your legal entities, revenue categories and account mapping, along with the responsibilities of the finance team. These services do not necessarily share identical synchronization behavior, so discuss the current scope for the accounting system you use.

RunMags eSign supports electronic signatures for advertising contracts. Evaluate signing as part of the agreement's complete journey, from the proposal through fulfillment and billing. The product includes contract and signing capability; you do not have to assume a separate e-sign provider is required for ordinary RunMags advertising agreements.

Website and communication requirements

WordPress is another approved integration option. Explain the reader or advertiser journey your website needs and how it should connect with publishing records. Review email delivery and reputation requirements separately, including sender identity and the people who will maintain the process. A list of services is a starting point for a configuration discussion, not a guarantee that every external plugin or custom workflow is already supported.

Prepare for a useful walkthrough

Choose representative records and define the result your team expects from the connection. Identify the source system, the receiving workflow and who will check exceptions. Keep account credentials and private customer data out of an initial website enquiry. Review integration planning, accounting workflows and onboarding, or book a demo to discuss your requirements.

Before enabling a new connection, agree the result your team expects and the staff member who will check it. Clear ownership makes an integration easier to maintain and helps distinguish an operational question from a setup requirement when you need support.