Automate GSMTasks Project

What GSMTasks Project is

The GSMtasks API is a RESTful web service for developers to programmatically interact with GSMtasks data, real-time delivery and task management and route optimization functionality.

What HumDay can do in GSMTasks Project

144 documented operations change something in GSMTasks Project. The 77 most useful are listed here.

• PUTAction to (re)set the account stripe customer and payment method to new values./accounts/{id}/stripe_attach_payment_method/
• PUTDetached payment method from the customer./accounts/{id}/stripe_detach_payment_method/
• POSTAction to start a new setup intent./accounts/{id}/stripe_create_setup_intent/
• PUTAction to start a new setup intent./accounts/{id}/stripe_create_setup_intent/
• PUTAction to set a payment method to default./accounts/{id}/stripe_set_default_payment_method/
• POSTAvailable from version 2.4.2/documents/batch_delete/
• POSTAvailable from version 2.4.2/signatures/batch_delete/
• POSTUpdate tasks/tasks/
• POSTUpdate users/users/
• POSTUpdate emails/emails/
• POSTUpdate orders/orders/
• POSTUpdate reorder/tasks/reorder/
• POSTUpdate reposition/tasks/reposition/
• PATCHUpdate id/tasks/{id}/
• PUTUpdate id/tasks/{id}/
• DELETEDelete id/users/{id}/
• PATCHUpdate id/users/{id}/
• PUTUpdate id/users/{id}/
• DELETEDelete id/emails/{id}/
• PATCHUpdate id/emails/{id}/
• PUTUpdate id/emails/{id}/
• PATCHUpdate id/orders/{id}/
• PUTUpdate id/orders/{id}/
• POSTUpdate sms/sms/
• POSTUpdate routes/routes/
• POSTUpdate clients/clients/
• POSTUpdate devices/devices/
• POSTUpdate exports/exports/
• POSTUpdate reviews/reviews/
• POSTUpdate register/register/
• POSTUpdate trackers/trackers/
• POSTUpdate webhooks/webhooks/
• POSTUpdate documents/documents/
• POSTUpdate formrules/formrules/
• POSTUpdate metafields/metafields/
• POSTUpdate signatures/signatures/
• POSTUpdate task forms/task_forms/
• POSTUpdate fail/tasks/{id}/fail/
• POSTUpdate recurrences/recurrences/
• POSTUpdate task import/task_import/
• POSTUpdate authenticate/authenticate/
• POSTUpdate client roles/client_roles/
• POSTUpdate file uploads/file_uploads/
• POSTUpdate integrations/integrations/
• POSTUpdate accept/tasks/{id}/accept/
• POSTUpdate assign/tasks/{id}/assign/
• POSTUpdate cancel/tasks/{id}/cancel/
• POSTUpdate reject/tasks/{id}/reject/
• POSTUpdate account roles/account_roles/
• POSTUpdate resend/emails/{id}/resend/
• POSTUpdate notifications/notifications/
• POSTUpdate task commands/task_commands/
• POSTUpdate transit/tasks/{id}/transit/
• DELETEDelete on duty/users/{id}/on_duty/
• PUTUpdate on duty/users/{id}/on_duty/
• POSTUpdate working state/working_state/
• POSTUpdate password reset/password_reset/
• POSTUpdate activate/tasks/{id}/activate/
• POSTUpdate complete/tasks/{id}/complete/
• POSTUpdate unaccept/tasks/{id}/unaccept/
• POSTUpdate unassign/tasks/{id}/unassign/
• POSTUpdate time locations/time_locations/
• POSTUpdate activate/users/{id}/activate/
• POSTUpdate password change/password_change/
• POSTUpdate contact addresses/contact_addresses/
• POSTUpdate users on duty log/users_on_duty_log/
• POSTUpdate push notifications/push_notifications/
• POSTUpdate notify/client_roles/{id}/notify/
• POSTUpdate route optimizations/route_optimizations/
• POSTUpdate task import mapping/task_import_mapping/
• POSTUpdate notify/account_roles/{id}/notify/
• POSTUpdate account change/tasks/{id}/account_change/
• POSTUpdate contact address import/contact_address_import/
• POSTUpdate notification templates/notification_templates/
• POSTUpdate password reset confirm/password_reset_confirm/
• POSTUpdate time location features/time_location_features/
• POSTUpdate schedule/route_optimizations/{id}/schedule/

What HumDay can read from GSMTasks Project

These are the operations a schedule or a trigger can watch.

• GETMixin which allows the override of the filename being passed back to the user when the spreadsheet is downloaded./task_events/
• GETMixin which allows the override of the filename being passed back to the user when the spreadsheet is downloaded./task_events/{id}/
• GETFetch all customer payment methods./accounts/{id}/stripe_payment_methods/
• GETThis view has multiple renderer classes available: json and xlsx./task_exports/
• GETThis view has multiple renderer classes available: json and xlsx./contact_address_exports/
• GETOpenApi3 schema for this API./docs/schema/
• GETFetch a single payment method from stripe./accounts/{id}/stripe_get_payment_method/
• GETFetch existing setup intents/accounts/{id}/stripe_setup_intents/
• GETFetch a single setup intent/accounts/{id}/stripe_get_setup_intent/
• GETFetch a single setup intent/accounts/{id}/stripe_get_setup_attempt/
• GETRead tasks/tasks/
• GETRead users/users/
• GETRead emails/emails/
• GETRead orders/orders/
• GETRead events/tasks/{id}/events/
• GETRead id/tasks/{id}/
• GETRead id/users/{id}/
• GETRead id/emails/{id}/
• GETRead id/orders/{id}/
• GETRead sms/sms/
• GETRead addons/addons/
• GETRead routes/routes/
• GETRead states count/reports/tasks/states_count/

How automating GSMTasks Project works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live GSMTasks Project account.
4. Grant access, then go live. You approve the specific GSMTasks Project operations it may use — and only those.

Questions about GSMTasks Project automation

Can HumDay connect to GSMTasks Project?

Yes. HumDay reads GSMTasks Project's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 261 operations are documented.

Do I need to write code to automate GSMTasks Project?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your GSMTasks Project account.

What can HumDay do in GSMTasks Project?

144 of the 261 documented operations change something in GSMTasks Project, and 117 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my GSMTasks Project account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to GSMTasks Project is held behind that approval.

Where this came from

The operations above are read from a published API description for GSMTasks Project at raw.githubusercontent.com/oeklo/gsmtasks-schema/v2.4.13/GSMTasks.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.