[{"data":1,"prerenderedAt":140},["ShallowReactive",2],{"doc:\u002Fv\u002F2026.3\u002Fadmin\u002Fintegrations-and-api":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"section":10,"version":11,"lastUpdated":12,"body":13,"_type":134,"_id":135,"_source":136,"_file":137,"_stem":138,"_extension":139},"\u002Fv\u002F2026.3\u002Fadmin\u002Fintegrations-and-api","admin",false,"","Integrations and API","Connect Workspace369 with external systems through supported integrations, inbound and outbound APIs, and controlled public links.","Administration","2026.3","2026-07-11",{"type":14,"children":15,"toc":125},"root",[16,24,31,36,42,47,53,83,89,94,100,105,111,116],{"type":17,"tag":18,"props":19,"children":20},"element","p",{},[21],{"type":22,"value":23},"text","Integrations should exchange the minimum information required for a clear business outcome. Decide which system owns each record before creating a two-way workflow.",{"type":17,"tag":25,"props":26,"children":28},"h2",{"id":27},"choose-the-system-of-record",[29],{"type":22,"value":30},"Choose the system of record",{"type":17,"tag":18,"props":32,"children":33},{},[34],{"type":22,"value":35},"For every integration, identify where the authoritative client, project, communication, billing, product, or file data lives. Two systems should not both overwrite the same field without an explicit conflict policy.",{"type":17,"tag":25,"props":37,"children":39},{"id":38},"use-supported-connection-types",[40],{"type":22,"value":41},"Use supported connection types",{"type":17,"tag":18,"props":43,"children":44},{},[45],{"type":22,"value":46},"Workspace369 can support integration workflows through available native connections, inbound APIs, outbound APIs, and controlled public links. Availability can depend on the module, plan, and integration.",{"type":17,"tag":25,"props":48,"children":50},{"id":49},"protect-credentials-and-client-data",[51],{"type":22,"value":52},"Protect credentials and client data",{"type":17,"tag":54,"props":55,"children":56},"ul",{},[57,63,68,73,78],{"type":17,"tag":58,"props":59,"children":60},"li",{},[61],{"type":22,"value":62},"Store credentials only in the supported secure configuration.",{"type":17,"tag":58,"props":64,"children":65},{},[66],{"type":22,"value":67},"Use the narrowest permissions required.",{"type":17,"tag":58,"props":69,"children":70},{},[71],{"type":22,"value":72},"Do not place private credentials in public links, client-visible fields, or browser code.",{"type":17,"tag":58,"props":74,"children":75},{},[76],{"type":22,"value":77},"Review what client and workspace information leaves Workspace369.",{"type":17,"tag":58,"props":79,"children":80},{},[81],{"type":22,"value":82},"Rotate credentials when ownership changes or exposure is suspected.",{"type":17,"tag":25,"props":84,"children":86},{"id":85},"design-reliable-synchronization",[87],{"type":22,"value":88},"Design reliable synchronization",{"type":17,"tag":18,"props":90,"children":91},{},[92],{"type":22,"value":93},"Define what happens when a request is duplicated, delayed, retried, or delivered out of order. Use stable record identifiers and make failed synchronization visible to an owner.",{"type":17,"tag":25,"props":95,"children":97},{"id":96},"use-public-links-carefully",[98],{"type":22,"value":99},"Use public links carefully",{"type":17,"tag":18,"props":101,"children":102},{},[103],{"type":22,"value":104},"Public links are useful for client-facing requests, proposals, payments, intake forms, and other controlled workflows. Share only the intended record and action rather than exposing the full internal workspace.",{"type":17,"tag":25,"props":106,"children":108},{"id":107},"validate-before-production",[109],{"type":22,"value":110},"Validate before production",{"type":17,"tag":18,"props":112,"children":113},{},[114],{"type":22,"value":115},"Test with non-sensitive sample records. Confirm field mapping, ownership, timezone behavior, retry handling, and the exact information visible to each external participant.",{"type":17,"tag":117,"props":118,"children":119},"blockquote",{},[120],{"type":17,"tag":18,"props":121,"children":122},{},[123],{"type":22,"value":124},"Integration troubleshooting should include the connection name, affected record, expected direction, time of the attempt, and response status. Never send private API keys to support by email.",{"title":7,"searchDepth":126,"depth":126,"links":127},2,[128,129,130,131,132,133],{"id":27,"depth":126,"text":30},{"id":38,"depth":126,"text":41},{"id":49,"depth":126,"text":52},{"id":85,"depth":126,"text":88},{"id":96,"depth":126,"text":99},{"id":107,"depth":126,"text":110},"markdown","content:v:2026.3:admin:integrations-and-api.md","content","v\u002F2026.3\u002Fadmin\u002Fintegrations-and-api.md","v\u002F2026.3\u002Fadmin\u002Fintegrations-and-api","md",1783880375078]