Skip to content

Activate process

Endpoint

PUT /organizations/{org_id}/runs/{run_id}/activate

This endpoint restores (unarchives) a previously archived Tallyfy process instance (run), making it active again.

Request

Replace {org_id} with your Organization ID and {run_id} with the ID of the process run to activate.

Headers

  • Authorization: Bearer {your_access_token}
  • Accept: application/json
  • X-Tallyfy-Client: APIClient

Body

No request body is needed for this PUT request.

Code samples

const accessToken = 'YOUR_PERSONAL_ACCESS_TOKEN';
const orgId = 'YOUR_ORGANIZATION_ID';
const runId = 'PROCESS_RUN_ID_TO_ACTIVATE';
const apiUrl = `https://go.tallyfy.com/api/organizations/${orgId}/runs/${runId}/activate`;
const headers = new Headers();
headers.append('Authorization', `Bearer ${accessToken}`);
headers.append('Accept', 'application/json');
headers.append('X-Tallyfy-Client', 'APIClient');
fetch(apiUrl, {
method: 'PUT', // Use PUT method
headers: headers
// No body required for this request
})
.then(response => {
return response.json().then(data => { // Attempt to parse JSON regardless of status
if (!response.ok) { // Expect 200 OK on success
console.error(`Failed to activate process ${runId}:`, data);
throw new Error(`HTTP error! status: ${response.status}`);
}
console.log(`Successfully activated process ${runId}. Status: ${response.status}`);
return data; // Activation returns the updated process
});
})
.then(data => {
console.log('Activated process details:');
console.log(JSON.stringify(data, null, 2));
})
.catch(error => {
console.error(`Error activating process ${runId}:`, error.message);
});

Response

A successful request returns a 200 OK status code. The response body contains the details of the reactivated Tallyfy process run, with the archived_at timestamp removed and the status updated to its pre-archive state.

{
"data": {
"id": "PROCESS_RUN_ID_TO_ACTIVATE",
"name": "Restored Project Run",
"status": "active", // Or 'complete', etc.
"archived_at": null, // Timestamp is removed
// ... other process properties ...
"last_updated": "2024-05-22T11:00:00Z" // Reflects activation time
}
}

If the process run ID is not found, was not archived, or you lack permission, an error status code (404, 400, 403) will be returned.


Processes > Archive process

A DELETE endpoint archives process instances by hiding them from default views while retaining data for future restoration through authenticated API requests requiring organization and run IDs.

Processes > Delete process

The DELETE endpoint permanently removes a process run instance and its associated data including tasks comments and form values with no option for recovery.

Tasks > Reopen task

The endpoint allows reopening completed tasks by using DELETE requests to restore them to an active state with proper authentication headers and supports both process-run tasks and standalone one-off tasks through distinct URL patterns.

Code Samples > Managing processes (Runs)

The API facilitates process management by enabling users to launch retrieve update and control the lifecycle of running instances while providing integration capabilities for tasks templates and organizational tags.