Your HTTP jobs,precisely scheduled.
Build webhook and API requests, run them once or on a recurring schedule, and inspect every recorded response from a focused operations workspace.
Schedule
Every 15 minutes
Recurring rate
Controls
Run on demand
Without changing schedule
{
"event": "sync.requested",
"source": "taskpulse"
}
One workspace
The controls you need to operate scheduled requests.
TaskPulse connects request configuration, scheduling, execution controls, and run detail without introducing workflow features you do not need.
Flexible scheduling
Choose a one-time execution, a recurring rate, or an EventBridge cron expression.
Complete HTTP requests
Configure method, URL, headers, JSON payload, timeout, retries, and supported authentication.
Inspectable run history
Review execution status, HTTP response, duration, timestamps, and errors for each recorded run.
Protected credentials
Bearer tokens, API keys, and signing secrets are encrypted before they are stored.
Simple by design
From endpoint to execution.
Configure the request once, then keep its schedule and history in view.
Build the request
Set the endpoint, method, headers, payload, and authentication.
Choose the timing
Run once, use an interval, or enter a cron expression in the timezone you choose.
Operate with context
Run on demand, pause a schedule, and inspect the result of every recorded execution.
Pricing
Start free. Pay only for what you run.
No subscriptions and no surprises — recurring schedules use prepaid invocation credits that never expire.
Free
For trying things out$0forever
Schedule up to 2 one-time webhook calls with full request configuration and run history.
- Up to 2 scheduled jobs
- One-time schedules
- Run now, pause, and delete controls
- Full run history with response logs
- Encrypted authentication secrets
Pay As You Go
Most flexible$1per 100 invocations
Buy credits up front, then run unlimited jobs on any schedule. Every recorded run uses one credit.
- Unlimited jobs
- One-time, rate, and cron schedules
- $1 per 100 invocations — prepaid credits
- Credits never expire
- Live balance and purchase history
- Pay by card, UPI, netbanking, or wallet
$10.00for 1,000 runs
Top up from your Account page with Stripe or Razorpay.
Answers first
Frequently asked questions
Scheduling, payments, authentication, and troubleshooting — the short version.
Create an account, open the request builder, and enter your endpoint URL, method, headers, and JSON payload. Then pick a schedule — a one-time date, a repeating interval like every 15 minutes, or a cron expression — and save. Use the Run now button to test the job immediately without waiting for the schedule.
Three: one-time schedules that run once at an exact local date and time, rate schedules that repeat every N minutes, hours, or days, and six-field cron expressions for calendar rules such as “weekdays at 09:00”. Every schedule runs in the IANA timezone you choose.
The Free plan lets you keep up to 2 one-time jobs — perfect for trying TaskPulse. Pay As You Go removes every limit: unlimited jobs of any schedule type at $1 per 100 invocations. You buy invocation credits up front, every recorded run consumes one credit, and your remaining balance is always visible on the Account page.
Credits can be purchased by card through Stripe Checkout or through Razorpay (cards, UPI, netbanking, and wallets). Payments are one-time top-ups, not subscriptions — there is nothing to cancel, and credits never expire.
Four options: no authentication, a Bearer token added to the Authorization header, an API key sent under a custom header name you choose, or a signed webhook where TaskPulse sends an HMAC-SHA256 signature your server can verify. Secrets are encrypted before storage and never appear in queue messages.
Open the job and check its run history. Every run records the HTTP status, response body, duration, and error message. Common causes: the endpoint returned a non-2xx status, the request exceeded its timeout (30 seconds max), or the URL points to a private network address, which TaskPulse blocks. Failed runs are retried automatically before landing in the dead-letter queue.
Existing schedules stay configured, but new runs are blocked until you top up — you will see a warning on your Account page before that happens. Add credits at any time and runs continue immediately; no configuration is lost.
Something else on your mind? Read the documentation