Integration
Connect MagicBlocks to SchedulingKit
When something happens in MagicBlocks, your agent does the next thing in SchedulingKit. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want MagicBlocks and SchedulingKit to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with MagicBlocks and SchedulingKit
Triggers and actions 1 trigger ยท 11 actions
Trigger
Contact Created or UpdatedTriggers when a contact is created or updated.
- Create Contact
Creates a contact in your workspace
- Find Contact
Finds a contact by id or email or phone from your workspace
- Get Contact
Get a single contact by id, email, or phone. GET /v1/contacts/{contactId}, /v1/contacts/email/{email}, /v1/contacts/phone/{phone}
- List Contacts
List all contacts in a MagicBlocks workspace. GET /v1/contacts
- Update Contact
Updates a contact in your workspace.
Action
Add invoiceCreate a new invoice. POST /api/v1/invoices
- Add location
Create a new location. POST /api/v1/locations
- Get invoice
Get a single invoice by id. GET /api/v1/invoices/{id}
- Get location
Get a single location by id. GET /api/v1/locations/{id}
- List locations
List the team's locations. GET /api/v1/locations
- Update location
Update an existing location. PUT /api/v1/locations/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.