You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a845f72
Browse filesBrowse the repository at this point in the historyBrowse files
|`status`| string | Spend limit status \(ACTIVE, EXPIRED, ARCHIVED\)|
891
+
|`status`| string | Spend limit status \(ACTIVE, EXPIRED, ARCHIVED, DELETED\)|
891
892
|`periodRecurrenceType`| string | Period recurrence \(PER_WEEK, PER_MONTH, PER_QUARTER, PER_YEAR, ONE_TIME\)|
892
893
|`spendType`| string | Spend type of the limit |
893
894
|`startDate`| string | Spend limit start date |
@@ -932,7 +933,7 @@ Create a new spend limit (hard-authorization card program) in the Brex account
932
933
|`currency`| string | No | ISO 4217 currency code for the base limit \(defaults to USD\)|
933
934
|`authorizationType`| string | Yes | Whether authorizations decline based on available balance \(HARD, SOFT\)|
934
935
|`rolloverRefreshRate`| string | Yes | Recurrence at which rolled-over unused funds stop rolling over \(OFF, NEVER, PER_MONTH, PER_QUARTER, PER_YEAR\)|
935
-
|`limitBufferPercentage`| number | No | Flexible buffer on the limit as a 0-100 percentage |
936
+
|`limitBufferPercentage`| number | No | Flexible buffer on the limit as a whole-number percentage from 0 to 100|
936
937
|`description`| string | No | Description of what the spend limit is used for |
937
938
|`parentBudgetId`| string | No | ID of the parent budget |
938
939
|`startDate`| string | No | Date the spend limit should start counting \(YYYY-MM-DD\)|
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/calendly.mdx
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Webhook subscriptions require a paid plan and the permissions for their user or
17
17
18
18
## Use the block [#usage-instructions]
19
19
20
-
Manage event types, scheduled events, invitees, and webhooks. Trigger workflows based on Calendly webhook events (invitee scheduled, invitee canceled, routing form submitted).
20
+
Manage event types, scheduled events, invitees, bookings, availability, and routing forms. Trigger workflows based on Calendly webhook events (invitee scheduled, invitee canceled, routing form submitted).
21
21
22
22
## Actions
23
23
@@ -93,12 +93,12 @@ Retrieve a list of all event types for a user or organization
93
93
94
94
| Parameter | Type | Required | Description |
95
95
| --------- | ---- | -------- | ----------- |
96
-
|`user`| string | No | Return only event types that belong to this user. Format: URI \(e.g., "https://api.calendly.com/users/abc123-def456")|
97
-
|`organization`| string | No | Return only event types that belong to this organization. Format: URI \(e.g., "https://api.calendly.com/organizations/abc123-def456")|
96
+
|`user`| string | No | Return event types available to this user. Either user or organization is required. Format: URI \(e.g., "https://api.calendly.com/users/abc123-def456")|
97
+
|`organization`| string | No | Return event types that belong to this organization. Either user or organization is required. Format: URI \(e.g., "https://api.calendly.com/organizations/abc123-def456")|
98
98
|`count`| number | No | Number of results per page. Format: integer \(default: 20, max: 100\)|
99
99
|`pageToken`| string | No | Page token for pagination. Format: opaque string from previous response next_page_token |
100
100
|`sort`| string | No | Sort order for results. Format: "field:direction" \(e.g., "name:asc", "name:desc"\)|
101
-
|`active`| boolean | No | When true, show only active event types. When false or unchecked, show all event types\(both active and inactive\). |
101
+
|`active`| boolean | No | When true, return only active event types. When false, return only inactive event types. When omitted, return all event types. |
102
102
103
103
#### Output
104
104
@@ -416,6 +416,8 @@ Book a meeting by creating an invitee on an event type at a chosen time. Require
416
416
|`inviteeLastName`| string | No | Last name of the invitee |
417
417
|`textReminderNumber`| string | No | Phone number for SMS reminders. Format: E.164 phone number \(e.g., "+14155551234"\)|
418
418
|`eventGuests`| json | No | Additional guests to copy on the invite. Format: array of email strings \(max 10, e.g., \["guest@example.com"\]\)|
419
+
|`location`| json | No | Meeting location. Must match a location configured on the event type; omit for round robin event types. Format: object with "kind" \(physical, inbound_call, outbound_call, zoom_conference, google_conference, gotomeeting_conference, microsoft_teams_conference, webex_conference, ask_invitee, custom\) and, for physical, outbound_call, ask_invitee and custom, a "location" string \(e.g., \{"kind": "outbound_call", "location": "+14155551234"\}\)|
420
+
|`questionsAndAnswers`| json | No | Answers to the event type's booking questions. Required questions must be answered, and each question must match the event type's question text exactly. Format: array of objects with "question", "answer" and "position" \(e.g., \[\{"question": "Company", "answer": "Acme", "position": 0\}\]\)|
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/datadog.mdx
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ Query metric timeseries data from Datadog. Use for analyzing trends, creating re
72
72
73
73
### Datadog Create Event
74
74
75
-
Post an event to the Datadog event stream. Use for deployment notifications, alerts, or any significant occurrences.
75
+
Post an event to the Datadog event stream. Use for deployment notifications, alerts, or any significant occurrences. Uses the v1 events endpoint, which Datadog has deprecated and serves only to organizations that have used it before.
76
76
77
77
<ReferenceDetails>
78
78
@@ -95,7 +95,8 @@ Post an event to the Datadog event stream. Use for deployment notifications, ale
95
95
| Parameter | Type | Description |
96
96
| --------- | ---- | ----------- |
97
97
|`event`| object | The created event details |
98
-
| ↳ `id`| number | Event ID |
98
+
| ↳ `id`| number | Event ID. Can lose precision above 2^53; prefer id_str |
99
+
| ↳ `id_str`| string | Event ID as an exact string |
99
100
| ↳ `title`| string | Event title |
100
101
| ↳ `text`| string | Event text |
101
102
| ↳ `date_happened`| number | Unix timestamp when event occurred |
@@ -280,7 +281,7 @@ Search and retrieve logs from Datadog. Use for troubleshooting, analysis, or mon
|`from`| string | Yes | Start time in ISO-8601 format or relative time \(e.g., "now-1h", "now-15m", "2024-01-15T10:00:00Z"\)|
282
283
|`to`| string | Yes | End time in ISO-8601 format or relative time \(e.g., "now", "now-5m", "2024-01-15T12:00:00Z"\)|
283
-
|`limit`| number | No | Maximum number of logs to return \(e.g., 50, 100, max: 1000\)|
284
+
|`limit`| number | No | Maximum number of logs to return \(default: 50, max: 5000\)|
284
285
|`cursor`| string | No | Pagination cursor from a previous call, taken from its nextLogId output. Omit for the first page. |
285
286
|`sort`| string | No | Sort order: "timestamp" for oldest first, "-timestamp" for newest first |
286
287
|`indexes`| string | No | Comma-separated list of log indexes to search |
@@ -476,6 +477,7 @@ Get the details of a single incident by ID. Requires the Incident Management `in
476
477
| ↳ `modified`| string | Last modification timestamp |
477
478
| ↳ `resolved`| string | Resolution timestamp |
478
479
| ↳ `time_to_resolve`| number | Seconds from creation to resolution |
480
+
|`included`| array | Related resources requested through include \(users, attachments\)|
479
481
480
482
</ReferenceDetails>
481
483
@@ -705,7 +707,7 @@ Update a service level objective. Reads the current SLO first and applies only t
705
707
| --------- | ---- | -------- | ----------- |
706
708
|`sloId`| string | Yes | The ID of the service level objective to update |
707
709
|`name`| string | No | New name for the SLO. Leave blank to keep the current name. |
708
-
|`type`| string | No | SLO type: "metric" or "monitor". Leave blank to keep the current type. Changing type requires supplying the matching query or monitorIds. |
710
+
|`type`| string | No | SLO type: "metric" or "monitor". Leave blank to keep the current type. Changing type requires supplying the matching query or monitorIds. Converting to a "time_slice" SLO is not supported. |
709
711
|`thresholds`| string | No | JSON array of thresholds replacing the stored ones, e.g. \[\{"timeframe": "30d", "target": 99.9, "warning": 99.95\}\]. Leave blank to keep the current thresholds. |
710
712
|`description`| string | No | Description of the SLO |
711
713
|`tags`| string | No | Comma-separated tags \(e.g., "env:prod,team:core"\)|
@@ -785,6 +787,7 @@ Get an SLO’s history over a time window, including the overall SLI value and r
785
787
| ↳ `monitors`| array | Per-monitor SLI data for multi-monitor SLOs |
786
788
| ↳ `thresholds`| object | Thresholds keyed by timeframe |
787
789
|`sliValue`| number | Overall SLI value over the window |
790
+
|`errors`| array | Errors Datadog hit while querying the history; the call can succeed with partial data |
0 commit comments