Verifying a connector
Verification is Elie proving it can actually sign in. It is the gate on everything useful: Engagement Status only becomes Connected when a check succeeds, and a connector that is not Connected cannot be enabled.
There are exactly two ways it happens, and which one you get is decided by the sign-in method you chose at creation — not by the kind of system. That is why an email connector can verify either way.
- The IntelieKonnect module visible in your left-hand navigation.
- This permission: IntelieKonnect — Update.
- A connector whose required credential fields are filled in.
If IntelieKonnect isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.
Which one does my connector use?
Open Configuration and select Edit Configuration. Whichever action appears is the one your connector uses.
| Action | Used by | How it behaves |
|---|---|---|
| Ping | SFTP, FTPS, email App Password, databases, most REST APIs | Immediate. Elie opens a connection while you wait and tells you the result. |
| Authenticate | Email Graph API, Google Drive, the accounting connectors | You are sent to the provider to sign in. Elie waits for the provider to answer. |
Ping — the immediate test
Ping runs a live connection attempt on the spot.
- It succeeds → Engagement Status becomes Connected and the time of the check is recorded.
- It fails → the connector stays Not Connected and the page shows why. Nothing else changes; your configuration is untouched.
Use Ping & Save to test and save together — see Configuring an import connector. Ping alone deliberately does not save, which is useful while you are still guessing at a host or port.
Ping is safe to repeat as often as you like. It reads nothing and imports nothing; it only opens a connection and closes it.
Authenticate — the provider handshake
Authenticate hands the sign-in to Google, Microsoft or your accounting provider.
Open the Configuration tab and select Edit Configuration. On a connector whose sign-in method uses OAuth, the verify control at the bottom of the form reads Authenticate rather than Ping — that is how you can tell which of the two you are dealing with without knowing the connector type. Select it: the connector moves to Verification Pending and your browser is sent to the provider.
Sign in with an account that can see the folder or mailbox you want, and accept the permissions Elie asks for. This screen belongs to the provider, not to Elie — its wording and its rules are theirs.
The provider returns you to Elie. Go to Overview and read Connector Details: Connector Status has left Verification Pending and returned to Initialised, and Engagement Status now reads Connected. That pair means the connector is verified and ready to enable.
While the handshake is in flight the connector sits in Verification Pending. If you close the provider tab or abandon the sign-in, it returns to Initialised on its own — you are not stuck, and you can start again.
:::caution The account you sign in with is the account Elie uses Whatever you authenticate as is the identity Elie will keep using. Signing in with your own account works, but the connector then depends on your access — and stops working when you change role or leave. For anything that should outlive you, authenticate with an account your administrator intends for integrations. :::
What success looks like
- Engagement Status reads Connected, on the Overview tab and in the list.
- Status is Initialised — verified, but not yet switched on. That is the expected next state; enabling is a separate, deliberate step.
- Enable becomes available.
If something goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Neither Ping nor Authenticate does anything. | A required credential field is empty. | Read the hint under the buttons; it names the fields still needed. |
| Ping fails with an authentication error. | The password is the account password, not an app-specific one. | Generate an app password with your provider and use that. |
| Ping fails with a timeout. | Host, port, or a firewall. | Confirm the host and that the port is the TLS one. A network that blocks outbound connections will time out no matter what you enter. |
| Status is stuck on Verification Pending. | The handshake was abandoned, or the provider never returned. | Wait — it falls back to Initialised by itself. Then select Authenticate again. |
| The provider shows a consent error, or an administrator-approval message. | Your organisation restricts third-party application consent. | Ask your administrator to approve it. If that is not possible, use a Ping-style connector instead — see Choosing a connector type. |
| Status reads Verification Failed. | The check ran and was refused. | Open Configuration, correct the credentials, and verify again. The message names the reason. |
| It was Connected and is now Not Connected. | Credentials lapsed — expired password, revoked app password, rotated key. | Re-verify. The connector stays Active and keeps its bindings, so nothing else needs redoing. |
Next
- Enabling and disabling — the step verification unlocks.
- Schedules — how often it runs once enabled.
- Connector statuses — the full badge reference.