Integrations
Integrations connect Qik to outside services: a payment gateway for taking payments, Google or Apple for "Sign in with…" buttons on your apps and websites, and Firebase Cloud Messaging for push notifications in your mobile apps. Each integration stores the keys that service gives you, in one place, so your forms and apps can use them.
How integrations work
An integration is a record in your organisation created from an integration type. The type decides which service it talks to and which details it needs. Each integration has two sets of details:
- Public Details — identifiers that are safe to share, such as a client ID or a publishable key.
- Private Details — secrets, such as a client secret, private key or secret API key.
Once created, an integration is used somewhere else: a form's payment settings point at a payment integration, and an application's settings point at its sign-in and push integrations.
Common integrations
| Integration | What it's for | Where you use it |
|---|---|---|
| Stripe (payment gateway) | Taking card payments on forms and selling tickets | A form's payment settings. See Payment Basics. |
| Google sign-in | "Sign in with Google" on your apps and websites | The application's Integrations tab, under OAuth Integrations |
| Apple sign-in | "Sign in with Apple" on your apps and websites | The application's Integrations tab, under OAuth Integrations |
| Firebase Cloud Messaging | Push notifications to your mobile app | The application's Integrations tab, under FCM Integration |
The full list of integration types you can choose from is shown when you create an integration.
Adding an integration
- Click System in the dashboard sidebar.
- In the Integrations panel, click New Integration.
- Click Select Integration Target and choose the type of integration you want, for example Google sign-in.
- Give the integration a clear title, such as "Google sign-in — Members App".
- Fill in the Public Fields and Private Fields with the details from the outside service.
- Save.
Then connect it where it's used, as described below. You'll find all your integrations later in the same Integrations panel on the System page.
Adding Google or Apple sign-in to an app
Sign-in integrations let people log in to your website or mobile app with their Google or Apple account.
1. Get the keys from the provider
- Google — in Google Cloud Console, go to APIs & Services → Credentials and create an OAuth client ID of type "Web application". You'll need its client ID and client secret.
- Apple — in your Apple Developer account, create a Services ID with Sign in with Apple enabled, and a Sign in with Apple key. You'll need the Services ID, your team ID, the key ID and the key file's contents.
2. Create the integration in Qik
Follow Adding an integration above, choosing the Google or Apple sign-in type, and enter the details in the matching fields.
3. Turn it on for the application
- Open the application (see Applications).
- Go to the Integrations tab.
- Under OAuth Integrations, add the integration you created.
- Save.
4. Register the redirect address with the provider
Google and Apple only send people back to addresses you have registered. For a website, the address is:
https://<your-site-domain>/api/user/oauth/google/callback (or …/apple/callback)
Add it under Authorised redirect URIs in Google, or the Services ID's Return URLs in Apple. Your site also needs sign-in buttons; Qikbot or a connected AI tool can set up the buttons and give you the exact redirect addresses for your application.
How sign-in matches existing people
- Google signs in an existing login that has the same email address. Anyone new gets a new login only if the application allows sign-up.
- Apple matches people by their Apple account, not by email. Someone who already has an email-and-password login should keep using it (or Google).
Push notifications
To send push notifications to a mobile app built on Qik, create a Firebase Cloud Messaging integration with the credentials from your Firebase project, then choose it as the FCM Integration on the application's Integrations tab.
Other application integrations
The application's Integrations tab also has a Google Tag Measurement ID field (it looks like G-XXXXXXXXXX) for adding Google Analytics to a website. It doesn't need a separate integration record.
Connecting other services
If the service you need isn't in the list, you can usually connect it with an action: actions can call other services' APIs and receive their webhooks. Keep API keys for those services in Global Variables rather than in the action's code.
Permissions
Integrations hold keys that can take payments or sign people in, so only give administrators and trusted builders permission to view or edit them. The System menu item only appears for people whose role lets them see integrations, applications, logs or custom fields. When Qikbot creates an integration, it always asks for your approval first.
Tips
- Use separate integrations for test and live keys, and name them clearly.
- If a provider's secret is changed or rotated, update the Private Fields on the integration straight away. Sign-in or payments stop working until the details match.