Sync Bitrix24 tasks with Keepr and log elapsed time back
What the integration does
One integration connects a Bitrix24 portal — or one workgroup in it — to one Keepr project. Inbound, Bitrix24 tells Keepr about its tasks: a new task becomes a task in the Keepr project, completing it (status “Completed”) archives the task, and resuming it restores the task. A task awaiting the creator’s control is not done yet, and deleting a task archives its task.
Outbound, Keepr adds tracked time to the task as elapsed time, with the exact seconds and the start of each time entry. An edit updates that record and deleting the entry removes it. Only time from the integration’s Keepr project is sent, never rounded.
Before you start
In Keepr you need to be an owner or admin of the organization, or a manager of the workspace that holds the project. Every plan includes integrations: Free runs one at a time, Team three, and Ultimate — trial included — as many as you need.
In Bitrix24 you need the right to create webhooks (usually a portal administrator). A box portal works the same way, as long as it can reach over HTTPS and Keepr can reach it back over the public internet.
Bitrix24 sends each event once and never resends it, so a change made while Keepr cannot be reached is not picked up later.
1. Create the integration in Keepr
Open Organization settings → Integrations and press “New integration”. Choose Bitrix24, the Keepr project its tasks go into, and the name it acts under: Keepr shows its actions as, for example, “Archived by Bitrix24 · Website”.
To cover one workgroup, enter its id — the number in its address, . Leave it empty to cover the whole portal; a task outside the workgroup is recorded and skipped.
2. Create the inbound webhook Keepr uses
Keepr reads tasks and adds elapsed time through a Bitrix24 inbound webhook, and Bitrix24 shows every record as made by the webhook’s user. Create it as a dedicated user who can see the tasks and track time in them, so records are not shown as yours. See Bitrix24’s guide to webhooks.
Under Applications → Developer resources → Other () → Inbound webhook, give it the Tasks (task) permission and save. Copy its URL, which looks like : it is a secret, so treat it like a password.
3. Add the outbound webhook in Bitrix24
Under Applications → Developer resources → Other () → Outbound webhook, paste the endpoint from the integration’s Inbound webhooks section as the handler URL, and pick the events Task added (ONTASKADD), Task updated (ONTASKUPDATE) and Task deleted (ONTASKDELETE).
Save it, then copy the application token it shows: saving replaces the one shown before. Bitrix24 sends this token with every event instead of a signature, which is how Keepr knows the event is your portal’s.
4. Give Keepr the webhook URL and the token
On the integration’s page, open Credentials and press “Set…” next to the Bitrix24 credential. Paste the inbound webhook URL and the outbound webhook’s application token, and save. There is no address to enter: Keepr takes the portal from the URL.
Keepr stores both encrypted and afterwards shows only their first characters. Until the token is set, Keepr refuses Bitrix24’s events. To change the token later, paste the URL again with it.
What Keepr sends
An entry is sent once it is finished — a running timer sends nothing until it stops — and only when its task is in the integration’s project and links to a task on that portal. Tasks the integration created link that way, and so do tasks started from the browser extension on a Bitrix24 task page.
Each entry gets one elapsed-time record with its seconds, its start and a comment naming the member. An edit updates that record, a moved start moves it, deleting the entry deletes it, and a record deleted by hand is added again the next time the entry changes.
Imported time is history and is never sent. The integration’s “Recently sent” list shows the latest entries, each with its task, the member, the time Bitrix24 holds for it, and whether the last send worked; a failed row says why and what to do.
Pause or revoke
The switch on the integration’s page turns it off without losing anything. While it is off, events are recorded but not acted on, and no time is sent: an entry saved during the pause is sent the next time it changes. Switching it back on takes a slot under your plan’s limit again.
“Remove” next to the Bitrix24 credential stops time reporting and leaves the inbound direction alone. Revoke is final: Keepr destroys the stored URL and token and acts on nothing more. Delete both webhooks in Bitrix24 as well.
If something goes wrong
Every event appears under the integration’s recent deliveries with what it did. A 401 in Bitrix24’s log means the application token does not match the one in Keepr, usually because it was copied before saving. “Couldn’t read the task” means the inbound webhook URL is missing, revoked, lacks the Tasks permission, or its user cannot see the task. “Another workgroup’s task” is a task outside the integration’s workgroup.
In “Recently sent”, “Credential rejected” means the inbound webhook was deleted or lost its permission, and “Issue not found” that the task was deleted or its user cannot see it. “Tool unreachable, retrying” clears on its own once the portal answers. A send that failed for good is tried again the next time the entry changes.