Integrations: everything your app is connected to
Integrations, in your dashboard menu, shows everything your app is connected to in one place: whether each connection works, when it was last tested and what failed lately. Each connection has a link to the page where you set it up: Set up when nothing is saved yet, otherwise Change.
What you see
The connections are grouped like this. You only see the ones your app uses.
- Website and content: Website or platform is your WordPress site and its Yallapp plugin, your Shopify shop or other platform, or your own API. If your app has no website, it says your content is managed in the dashboard and there is nothing to connect.
- Card payments: Payment provider, for apps that take card payments. It shows whether payments go through Yallapp or through your own iyzico, Kashier, Fawaterk, Stripe or PayPal account, and whether your keys are live or test keys. See Card payments.
- Sign-in codes: WhatsApp codes and Email codes, when Yallapp sends your app's sign-in codes. They show whether codes go out from Yallapp's number and email address, or from your own WhatsApp number and email server. See App users and sign-in.
- Notifications: Firebase notifications, your Firebase key (see Push notifications with Firebase), and Huawei notifications once you've added Huawei Push Kit.
- Stores: Google Play and App Store, and Samsung Galaxy Store, Huawei AppGallery and Xiaomi GetApps once you've saved their keys.
What each state means
- Connected: it's set up, and its last test, if it had one, worked. The card says what it's connected to, for example when the Yallapp plugin on your site last checked in.
- Needs attention: its last test failed, or your own WhatsApp number or email server couldn't send a code. When your own number or server fails, Yallapp sends the codes instead, and the card says when it happened.
- Not set up: nothing is saved yet. Without payment keys your app shows prices without a Pay button. Without a Firebase key your app's users get no notifications. Without a store key you upload the app yourself, or we do it for you.
- Waiting: our team is still setting up WordPress for you, or your site is saved but the Yallapp plugin isn't active there yet.
Test a connection
Your website or platform, your own payment keys, your Firebase key and Huawei Push Kit have a Test button. It asks the other side now, and nothing is sent to anyone. The card then shows Last tested with the date and the result, and the details when it failed. After a failed test the connection stays at Needs attention until a test works again. If you test many times in a row, wait a few minutes before the next one.
Some connections can't be tested here:
- WhatsApp codes and Email codes have Send a test instead. It opens App sign-in, where you send a test code or a test email to yourself. When it arrives, the warning goes away.
- Store keys are checked when a build uploads with them. If a store refuses a key, Builds & downloads says so: see When a build or a connection fails.
The daily checks
Once a day we check your website or platform, your own payment keys, your Firebase key and Huawei Push Kit, while your app's plan is active. A website that doesn't answer is tried a second time before it counts, so a slow moment isn't reported. On WordPress, the Yallapp plugin checks in twice a day: a site whose plugin hasn't checked in for three days needs attention too. If a payment provider can't be reached at all, nobody is told and it's checked again the next day.
When a check fails
When a connection that worked, or was never tested, fails its daily check, we tell you once:
- a notice on your Overview, for example "your payment keys need attention", with Open Integrations;
- a notification on your phone in Yallapp Business;
- an email, in the language you use on the dashboard, with what the check found and a link to Integrations.
Our team is told too. While the connection keeps failing, you aren't told again every day. The notice says what to do:
- Your app couldn't load its content from your site: open Integrations, see what failed and test it again.
- The Yallapp plugin hasn't checked in: make sure the plugin is active and your site is up.
- The payment provider didn't accept your keys: your app can't take card payments until you check the keys in your provider's panel.
- Google didn't accept your Firebase key: add a new key from Firebase.
- Huawei didn't accept your Push Kit app ID and secret: notifications can't reach Huawei phones until you fix them.
- Saved keys can't be read: save them again.
When it works again
Fix the connection on the page its card links to, then choose Test on Integrations. When the test works, or the next daily check does, the notice on your Overview closes by itself. It also closes if your app no longer uses that connection.
Recent errors
Website or platform, Payment provider, WhatsApp codes, Email codes and Firebase notifications show Recent errors: problems your app ran into with that connection over the last 30 days, the latest first. Each one shows how many times it happened and when it last did. When there were none, the card says "No errors in the last 30 days." If codes don't reach people, see Sign-in codes don't arrive.